Flow Schedules during Revision Pull

Integrator.io
1

Hi All,
Not sure what I'm doing wrong here or maybe there's a bug.

I've set the flow schedule to be ignored when doing a revision pull into my production. My flows are scheduled in Prod but not in Sandbox. However, I get conflict errors when trying to do a pull and I'm stuck. Why do I have conflicts if these fields should be ignored??

Am I missing something?

The image shows a code conflict in a version control system, indicating a difference in the "schedule" line between "Before pull" and "After pull" sections. (Captioned by AI)
The image shows a code conflict in a version control system, indicating a difference in the "schedule" line between "Before pull" and "After pull" sections. (Captioned by AI)1977×724 54.8 KB

2

@praveenbasani there should be no conflict in this case, right?

@davidgollom can you share a screenshot of your ignore rule?

3

Hey Tyler.
Here you go.

This image shows a settings interface where users can select fields to be ignored during a data pull, with some fields under "flow" already selected such as "disabled," "schedule," and "timezone." (Captioned by AI)
This image shows a settings interface where users can select fields to be ignored during a data pull, with some fields under "flow" already selected such as "disabled," "schedule," and "timezone." (Captioned by AI)1024×961 40 KB

4

Also, I did find a sort of work around. If I changed the source schedule from null to anything the conflict went away. Seems like maybe a bug exists when the source is missing the ignore rule doesn't work correctly.

5

@davidgollom can you show us the details (a screenshot) you see under 'conflicts' section there in the first image you shared?

6

Hi - Just catching up here.
I just got the updated version of Celigo. The old problem went away but now there's a new one. I'm ignoring the Schedule but the pull is trying to overwrite my production schedule with the null schedule from Sandbox.
Here are the rules:

The image shows a settings panel titled "Ignore fields during pull," where specific fields like "flow.disabled," "flow.schedule," and "flow.timezone" are selected to be ignored during a pull operation. (Captioned by AI)
The image shows a settings panel titled "Ignore fields during pull," where specific fields like "flow.disabled," "flow.schedule," and "flow.timezone" are selected to be ignored during a pull operation. (Captioned by AI)1007×1057 44.3 KB

And here's the proposed update:
The image shows a version control interface highlighting changes before and after a pull, with modifications in JSON code related to "Get NetSuite items" and "Flows," including updates to names and schedule settings. (Captioned by AI)
The image shows a version control interface highlighting changes before and after a pull, with modifications in JSON code related to "Get NetSuite items" and "Flows," including updates to names and schedule settings. (Captioned by AI)1972×1616 195 KB

This should be getting ignored.