--- title: Managing Schedulers in Activate slug: managing-schedulers-in-activate docTags: createdAt: 2026-03-19T02:53:48.491Z --- 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: :::BlockQuote 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: :::BlockQuote 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.