Schedules are typically used to run cache writers, which update the cache and enable flows with cache event triggers to run if there are changes. The minimum supported interval is 15 minutes. You typically do not need to add action processors, as they will run via Real Time Action Processing (RTAP). Actions without RTAP will need a schedule to run actions placed in the queue by flows.
You can run a schedule outside its regular interval by selecting the circular Play button.
Select a schedule to view its details, including its feature description, when it was created, how often it runs, and the services it runs. You can also change the schedule's interval.
If a schedule starts, the first thing it does is check if a previous iteration is still running. If true, it will skip that scheduled run.
If you choose the skip wait checkbox on a flow, the schedule will mark itself complete when everything else is complete, even if the flow is still running. That means it is theoretically possible on short intervals for the schedule to come around and start the flow again despite an iteration still running.
Edit the sequence column to change the order of associated tasks on the same schedule.
Integration schedules are the preferred schedule type for integration builders because they are deployed alongside an integration when it is added to a customer workspace.
There are three subtypes of integration schedules, as determined by the feature type.
Active Feature Schedules: A schedule for a feature used in active integration registrations in the customer workspace.
Maintenance Feature Schedules: A schedule for an active feature that is under maintenance and can only be run manually.
Onboarding Feature Schedules: A schedule for a feature that is in the process of being activated for a given workspace.
Before you create an integration schedule, you must add a service or on-demand flow to your workspace.
Workspace schedules are created in and limited to the workspace. They manage and automate workflows within a specific workspace. Workspace schedules have limited applications compared to integration schedules, as they can make the jobs out of sync with the integration definition.
Was this helpful? Give us feedback.