Managing Schedulers in Activate

schedulers in activate automate tasks by running actions at defined times they are commonly used for synchronisation, clean up processes, notifications, and workflow execution this guide explains how to configure and manage schedulers using the activate scheduler wizard overview a scheduler is a configurable resource that runs one or more actions follows a defined timetable can repeat throughout the day or run once can be limited to specific days or dates schedulers operate in the background and automatically determine the next time they should run based on your configuration accessing the scheduler wizard open an existing scheduler or create a new one to launch the activate scheduler wizard the wizard is divided into these key sections days run at recurring tasks specific dates only actions each section contributes to how and when the scheduler runs configuring when a scheduler runs days the days section defines which days the scheduler is allowed to run options include daily – runs every day weekdays – runs monday to friday other – manually select individual days if a day is not selected, the scheduler will not run on that day, even if all other settings match example if only monday to friday are selected, the scheduler will not run on weekends run at the run at setting defines the start time for the scheduler this is the time the scheduler becomes eligible to run on a valid day example if set to 7 00 am , the scheduler will begin at 7 00 am on each allowed day if recurrence is not enabled, the scheduler runs once at this time recurring tasks the recurring tasks section allows the scheduler to run multiple times during the day run every enable run every to repeat the scheduler at a defined interval common examples every 15 minutes every 30 minutes every 1 hour if not enabled, the scheduler runs only once per day stop at enable stop at to define when recurring executions should stop for the day this creates a daily execution window example start 7 00 am run every 1 hour stop at 5 00 pm the scheduler runs hourly between 7 00 am and 5 00 pm, then resumes the next valid day specific dates only the specific dates only field limits execution to certain days of the month enter values as a comma separated list 1,15 this means the scheduler will only run on the 1st and 15th of each month this setting works alongside the selected days both must allow execution example if the scheduler is limited to weekdays and the 1st falls on a weekend, it will not run configuring actions the actions section defines what the scheduler does when it runs each scheduler can include one or more actions, such as running a task triggering a workflow executing a script initiating a connector process actions are listed in order and can typically be managed using add remove move up move down unsupported actions in the wizard you may see the following message the actions cannot be edited because there is a parameter with an invalid type please edit the action parameters directly this indicates that at least one action is not supported by the wizard interface what this means the scheduler will still run as expected the action itself cannot be edited through the wizard the action must be managed directly in the resource configuration recommended approach review the action parameters directly confirm the action is correctly configured avoid removing or recreating the action unless necessary how scheduler timing works activate evaluates scheduler settings to determine when a job should run it considers whether the scheduler is enabled whether the current day is allowed whether the date matches any specified monthly dates the configured start time whether recurrence is enabled whether the current time falls within the allowed run window after each run, activate automatically calculates the next valid execution time no manual update is required enabling and disabling schedulers a scheduler must be enabled before it will run if disabled, it is ignored regardless of its configuration it is common to leave schedulers disabled while validating configuration testing actions preparing dependencies good practices use clear naming choose names that describe the purpose of the scheduler examples hourly user sync daily clean up month end processing morning notifications match frequency to workload avoid running tasks more frequently than necessary short intervals are suitable for lightweight processes, while heavier jobs should run less often avoid unnecessary overlap if a task takes time to complete, avoid very short recurrence intervals that could create contention or confusion use date restrictions carefully the specific dates only setting is useful for billing or reporting cycles but can make schedules harder to interpret if overused review unsupported actions if the wizard cannot edit an action, confirm how it is maintained before making changes to the scheduler common scheduling scenarios once every weekday days weekdays run at 7 00 am recurring not enabled runs once per weekday at 7 00 am every hour during business hours days weekdays run at 7 00 am run every 1 hour stop at 5 00 pm runs hourly throughout the working day twice per month run at 9 00 am specific dates only 1,15 runs on the 1st and 15th of each month continuous daily processing days daily run at 12 00 am run every chosen interval runs repeatedly throughout the day based on the selected interval troubleshooting if a scheduler is not running as expected, check the following the scheduler is enabled the correct days are selected the start time is correct recurrence settings are configured correctly the stop time is not limiting execution specific dates are not restricting the schedule unintentionally the configured action is valid and correctly defined example based on the wizard the scheduler shown in the wizard starts at 7 00 am runs every 1 hour is enabled for all days of the week may optionally stop later in the day if configured executes the listed action each time it runs the message about invalid action types indicates that the action cannot be edited through the wizard and must be managed directly summary schedulers control when actions run in activate the wizard allows you to define timing, recurrence, and execution rules without needing to manage runtime behaviour manually to manage schedulers effectively select the correct days define an appropriate start time use recurrence where needed control execution windows with stop times apply date restrictions only when required ensure actions are valid and maintainable schedulers, when configured correctly, provide a reliable way to automate operational tasks across the platform