You can run flows on-demand or schedule flows to run on a regular basis.
Important
Before you begin you should run a flow once to verify it works as expected before scheduling it to run repeatedly. Use the following steps to run a flow on-demand before setting up the scheduling rules in order to verify the flow works.
You must enable a flow in order for it to run. Enable the flow and then use the following steps to run it:
-
Click the integration tile for the flow.
-
Click the run icon in the Run column for the flow you want to run.
-
If the run icon next to your flow is unavailable, toggle the Enabled switch.
-
Confirm your choice in the popup window.
-
Click the run icon.
The flow will always run according to the time zone you select for the Flow schedule regardless of other time zone settings.
If you did not specify a time zone, the flow will automatically use the time zone configured in the account owner's profile to execute the run. If the owner has not selected a time zone for their account, the flow schedule assumes UTC.
The Celigo platform flow scheduler does not automatically account for daylight saving time (DST). If you schedule a flow to execute on November 1st at 1:30 AM Eastern TZ, and the local time reverts to 1:00 AM at 2:00 AM for DST, the flow will run a second time at the revised 1:30 AM time. Likewise, if you schedule a flow to run on March 14th, at 2:30 AM Eastern Standard TZ, and the clock advances to 3:00 AM, the flow will be skipped until the following day.
You can now run one, multiple, or all sources in a flow. For enabled flows with multiple sources, in Flow builder, on the top right click Run. In the Run this flow once window, under Run multiple sources in parallel/Run multiple sources sequentially, you have options to select and run either All sources or Selected sources.
For running Selected sources, click Select sources to view a drop down list of configured sources and select one, multiple, or all sources to run and click Start.
If you have set export execution mode as Parallel and selected one or more of the existing sources to run a flow and there are more sources which are not triggered, you can click the Run additional sources functionality to select one or more of the remaining sources and click Start to run them parallelly.
You can check or uncheck the Run next flow(s) after current flow completes checkbox when manually running an enabled flow that has subsequent next integration flows configured. This helps you control whether or not those subsequent flows should also run.
Important
-
For scheduled runs, all configured next integration flows will always execute automatically.
-
The Run Console displays all jobs related to the selected sources.
-
You can cancel all in-progress runs from the console.
Once you have established connections to both source and destination (or lookup) applications in Flow builder, click the Options overflow (...) in your source application flow step to choose Set as source for preview to control which export’s data is available when configuring downstream steps.
The selected source is clearly indicated.
Note
The first source is selected by default when multiple sources exist.
Changing the preview source dynamically updates downstream preview data, making validation more accurate. This feature works in both Test run and Enabled modes.
Understand flow scheduling rates
Schedule flows at a rate that will not overload your connection. The applications you are integrating have varying thresholds for the amount of data that can be imported or exported. Consult the API documentation provided by the platforms your integration communicates with to calculate appropriate connection loads. The flow scheduler has presets for automatic flow scheduling and also supports Cron expressions for more complex flow scheduling.
Know your web service resources
The NetSuite Concurrency Governance settings may not handle aggressive web service requests, which are based on NetSuite user concurrency and/or account concurrency settings. While you may have found a workaround for this scenario, verify that you understand how NetSuite handles web services. For more information on NetSuite concurrency governance, see Govern Concurrency with NetSuite.
To capture details from an earlier date (than the current date) in your flow, you can backdate and run the flow. You can consider this option if your flows get stuck, details to be captured are missed, or the like.
(In Integration apps, backdating and running the flow does not create duplicate records. However, note this limitation in the Shopify payout reconciliation add-on.)
A flow must have a delta export if you want to backdate and run it. The delta export enables you to get records from a previous date and time to the current time. Delta exports are useful for syncing systems efficiently by minimizing the volume of data being exported and processed.
When running a flow manually, keep in mind that:
-
Only changes made after the selected “From date” will be considered.
-
Any unsynced changes from before that date will be skipped.
Follow these steps to backdate and run a delta flow:
-
Enable the flow: Select the flow in the Flows list of an integration; or, click the flow name to open it in Flow builder. Turn on the Enable (
) toggle and click Enable when the confirmation message is shown. See also, the above Run flows section.
-
Run the flow: Click the Run icon (
) in the Flows list or in Flow builder. In the Delta flow window that opens, choose Custom. Then, select your Time zone, and click the calendar icon to select the Start date. Here, you can choose an earlier date than the current date to backdate the flow. Enter Time, and click Run to run and check the flow.
-
Open the integration that contains the flow you want to schedule.
-
Click the calendar icon in the Schedule column.
Set the schedule according to your business needs.
If you choose to schedule your flow with Presets, you can select one of the following options from the Frequency drop-down list:
-
Once weekly
-
Once daily
-
Twice daily (every 12 hours) - This option requires a minimum of 12 hours between flow runs. Use cron scheduling to create schedules that run twice daily with less than 12 hours between flow runs.
-
Every eight hours
-
Every six hours
-
Every four hours
-
Every two hours
-
Every hour
-
Every 30 minutes
-
Every 15 minutes
You can use cron expressions to schedule Celigo flows. For more information on cron scheduling options, see Cron expression syntax.
Use the following steps to build a cron schedule in the Celigo platform:
-
Select the integration.
-
From the Flows tab, select the schedule icon (
) on the Schedule column.
-
Select the Use cron expression radio button.
Important
When you select a cron expression, the flow is set to run every 5 minutes by default. To make sure your flow runs only at the time you want, update the default setting from "every 5 minutes" to your preferred frequency schedule.
-
Minute
-
Every n minutes: Use the slider to set the schedule frequency in minutes (5 to 55). The flow runs at the cadence you choose.
-
Each selected minute: Click 10, 25, 40, or 55 to set the schedule frequency to run at a specific minute of every hour. For example, if the schedule frequency is set to 25, the flow runs on the 25th minute of each hour.
-
-
Hour
-
Every hour: The flow runs every hour.
-
Every n hours: Use the slider to set the schedule frequency in hours (1 to 23). The flow runs at the cadence you choose.
-
Each selected hour: Click the hour (00 to 23) to set the schedule frequency to run at a specific hour of every day. For example, if the schedule frequency is set to 03, 05, and 17, the flow runs at the 3rd, 5th, and 17th hours of each day.
-
-
Day of month
-
Every day: The flow runs every day.
-
Each day: Click the day of the month (01 to 31) to set the schedule frequency to run at a specific day every month. For example, if the schedule frequency is set to 02, 13, and 31, the flow runs at the 2nd, 13th, and 31st day of each month.
-
-
Month
-
Every month: The flow runs every month.
-
Each selected month: Click the month (Jan to Dec) to set the schedule frequency to run at a specific month every year. For example, if the schedule frequency is set to March, and Aug, the flow runs only in March and August each year.
-
-
Day of week
-
Every Week: The flow runs every week.
-
Each Week: Click the day of the week (01 to 31) to set the schedule frequency to run at a specific day every week. For example, if the schedule frequency is set to Tuesday and Thursday, the flow runs on Tuesday and Thursday of each week.
-
Click Reset to clear the expression field.
If you want a flow to run immediately after another flow is complete, open the flow that you want to trigger the next flow and click the Settings ( ) button in the upper right corner. From the Settings panel, select the flow you want to run next from the Next integration flow drop-down menu.
Once you have assigned a schedule to a flow, a blue dot on the schedule icon in the Flows tab and in the upper right corner of Flow Builder indicates that a schedule has been applied.
Flows tab schedule icon
Flow Builder schedule icon
If a flow has multiple source export flow steps, and the overall flow is scheduled to run at a certain frequency (every eight hours for example), then each source export will run in succession according to the flow schedule. If you want a specific source export to run at an alternate frequency from the overall flow schedule (every hour for example), you can override the flow schedule and apply a different schedule to the source export flow step.
Use the following steps to override a flow schedule for a specific source export:
-
Click + on the flow step and click the schedule icon (
-
Configure the flow schedule settings that will apply only to this source export flow step. Flow schedule override options are identical to those available when scheduling a flow.
Considerations when overriding flow schedules:
-
Override flow schedule settings are only applied to the source flow step on which they were configured. If a flow is set to run on a schedule, and one of the source exports has a schedule override applied, only that source export will send data into the flow based on the schedule override settings. Any other source exports that do not have flow schedule overrides configured will export data based on the general flow schedule settings.
-
Override flow schedule settings have precedence over general flow schedule settings. If all source export flow steps in a flow have override flow schedule settings applied, any scheduling settings applied to the overall flow are ignored.