Scheduling tasks

Edit online

Create schedules to run tasks at specific times or intervals and reduce manual work.

Task scheduling helps you automate repetitive work by configuring agents to run automatically. You can schedule:

  • Personal tasks: Timesheets, reminders, or routine activities.
  • Team workflows: Weekly reports, monthly reviews, or periodic notifications.
  • Automated processes: Email triage, data syncs, or system monitoring.

Schedules run in the background and deliver results directly to your chat interface.

Before you begin

Before you schedule tasks, ensure that:

  • The agent that you use has scheduling enabled. You can ask the agent to confirm, for example, "Do you have scheduling enabled?". Contact your administrator or agent builder to enable.
  • You have permission to access the agent and any workflows you want to schedule.

Creating a schedule

Use natural language to tell the agent what you want to schedule. Be specific and provide clear, detailed prompts for best results:

"Schedule a daily standup reminder every weekday at 9 AM"
"Run the sales report every Monday at 5 PM"
"Check the support inbox for urgent emails every hour"

Based on your prompt, the agent can:

  1. Recognize your scheduling intent.
  2. Present an interactive form with pre-populated fields based on your request.
  3. Guide you through configuration options.
  4. Confirm when the schedule is created.

Configuring the schedule

Provide the prompt and the date and time that the agent must run:

  • Prompt: The task description or instruction for the agent.
  • Status:
    • Active: The schedule runs automatically on the defined recurrence.
    • Inactive: The schedule is paused.
  • Frequency: Choose how often the schedule runs:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly

If you want to run an agentic workflow along with your prompt, select the agentic workflow in the Advanced settings (optional) section:

  • Select an agentic workflow: Choose a specific agentic workflow from the list. It lists only workflows that have scheduling enabled. For more information, see Scheduling agentic workflows in chat.
  • No workflow: The schedule runs the agent with the prompt that you provide.
  • Input parameters: If you select a workflow, provide required inputs or leave blank.
Figure 1. Schedule configuration form showing all available settings.

Screenshot of schedule configuration interface displaying basic settings including prompt field and status, and workflow selection dropdown.
Note: The workflow list shows only workflows that support scheduling. Add the workflows to the agent and deploy them to the live environment.

Timing

  • Time: A specific time of day, such as 9:00 AM or 5:30 PM.
  • Days: The days to run for weekly schedules, or the date to run for monthly schedules.
  • Timezone: Your local timezone.
  • Start date: When the schedule begins. It defaults to today.
  • End date: When the schedule stops (optional). For temporary schedules, set an end date to avoid unnecessary runs.

Review the details, optionally enter input parameters, and click Save.

Figure 2. Schedule configuration form showing timing settings.

Screenshot of schedule configuration interface displaying timing options with time and timezone fields.
Tip: Create a test schedule with a near-term run time to verify that it works as expected before you set up a long-term schedule.

Viewing all schedules

To list your active and paused schedules, use a prompt such as:

"Show my schedules"
"List all my scheduled tasks"

The agent shows a list of your schedules so that you can quickly identify the one that you want to manage. The list includes the schedule status, prompt, timing, and next occurrence. You can select a schedule from the list to view details, edit, or delete the schedule.

To view detailed information about a specific schedule, prompt the agent so that you can confirm that you have the right task before you take action:

"Show me the daily report schedule"
"View details for the monitoring schedule"

Schedule status

View and change schedule status in your schedules list. A schedule can have one of the following statuses:

  • Active: The schedule runs at the scheduled times.
  • Paused: You paused the schedule manually.
  • Completed: The schedule reached its run limit and stopped automatically.

Updating a schedule

To update a schedule, prompt the agent to identify the task, show the current configuration, let you edit the settings, and save your changes:

"Change the daily report to 9 AM instead of 7 AM"
"Update the sales report to run on Fridays instead of Mondays"

You can modify an existing schedule by updating the prompt text, workflow selection, schedule timing such as time, days, and dates, and the status.

Pausing and resuming schedules

To pause or resume a schedule, edit it. Ask the agent to show you the schedule details:

"Show me the monitoring schedule"

From the schedule details view, open the schedule for editing and change its status to control whether it runs. Set the status to Inactive to pause the schedule or to Active to resume it.

Deleting a schedule

Delete schedules that you no longer need to keep your list manageable and avoid unnecessary runs. To delete a schedule, ask the agent to show the schedule details or list your schedules:

"Show me the monitoring schedule"
"List all my schedules"

From the schedule view, delete the schedule that you no longer need and confirm the deletion when prompted.

Figure 3. Schedule deletion confirmation dialog.

Confirmation dialog box asking user to confirm schedule deletion with warning message.
Important: Deleting a schedule is permanent and cannot be undone.

Schedule execution

Receiving results

After each scheduled run, the system posts results to the original chat thread where you created the schedule. If the original thread is unavailable, the system creates a new agent thread. If the execution requires human input, the system sends a notification in the chat thread.

Note: The system posts results only when there is output to display. It does not send a completion message for every run.

Multiple user activities

When multiple scheduled tasks require user input in the same chat thread, the system queues the activities, lets you choose which ones to work on, and opens a new thread for later notifications if you close the original thread.

Viewing execution history

Regularly check execution logs to ensure that schedules run successfully and to identify issues. To check the history of your scheduled runs, use a prompt such as:

"Show me the logs for the daily report schedule"
"View execution history for the sales report"

The agent shows a log table so that you can review how the schedule runs over time. The table includes the execution status, the start time, and the instance ID for each run. From there, you can move through the history, open detailed flow analysis for specific runs when available, and identify patterns or issues.

Figure 4. Schedule run history showing run status, timestamps, and instance ID.

Schedule run history showing run status, timestamps, and instance ID.
Trouble: If a schedule does not run as expected, use the execution history to look for error messages, confirm that the schedule ran, and verify whether the workflow produced visible output.

Schedule timing

Date and time interpretation

The agent interprets natural language for dates and times:

  • Relative dates: "tomorrow", "next Friday", "in 2 weeks"
  • Time expressions: "morning" (9 AM), "afternoon" (2 PM), "end of day" (5 PM)
  • Specific times: "9:30 AM", "17:00", "5 PM EST"

Timezone handling

  • Default timezone: Your local timezone is automatically detected.
  • Explicit timezone: You can specify a different timezone, for example, "9 AM EST" or "5 PM Pacific".
  • Daylight Saving Time: The system handles it automatically, and your schedule times remain consistent in local time.
  • Timezone changes: If you change timezones, existing schedules keep their original timezone.
Tip: Always specify a timezone for schedules that involve multiple time zones or require precise timing.
Trouble: If schedules run at unexpected times, check the timezone in the schedule details, remember that the system handles Daylight Saving Time automatically, and edit the schedule if you need to change its timezone.

Recurrence patterns

Use these common recurrence patterns:

  • Daily: "every day at 7 AM"
  • Weekdays: "every weekday at 9 AM"
  • Weekly: "every Monday at 5 PM"
  • Monthly: "first day of every month at 9 AM"
  • Hourly: "every hour" or "every 2 hours"

Schedule limits and quotas

Execution limits by recurrence

To help ensure system reliability, execution limits vary by recurrence:

Recurrence Maximum executions Minimum interval
Every minute 100 5 minutes
Hourly 500 -
Daily Unlimited -
Weekly Unlimited -
Monthly Unlimited -

In summary, the following execution limit behavior applies:

  • Very frequent schedules that run every minute are limited to 100 executions and must run at least 5 minutes apart.
  • Hourly schedules can run up to 500 times.
  • Daily, weekly, and monthly schedules have no execution limit.

The system automatically applies the appropriate limit based on the schedule recurrence and displays it during creation.

Trouble: If a schedule does not run, check whether it reached its execution limit. Very frequent schedules have limits, so review the configured recurrence and maximum number of runs in the schedule details.

Examples

Example 1: Daily personal reminder

Scenario: Get a reminder to submit your timesheet every Friday.

User: "Remind me to submit my timesheet every Friday at 4 PM"

Result: The schedule:

  • Runs every Friday at 4:00 PM.
  • Sends a reminder message.
  • Continues until you delete it.

Example 2: Weekly team report

Scenario: Generate a sales report every Monday morning.

User: "Schedule the sales report workflow to run every Monday at 9 AM with region set to Northeast"

Result: The schedule:

  • Runs the sales report workflow.
  • Runs every Monday at 9:00 AM.
  • Uses "Northeast" as the region parameter.
  • Continues until you set an end date or delete it.

Example 3: Hourly monitoring

Scenario: Check the support inbox for urgent emails.

User: "Check the support inbox for urgent emails every hour"

Result: The schedule:

  • Runs every hour.
  • Checks for urgent emails.
  • Flags items that require attention.
  • Is limited to 500 executions.

Example 4: Monthly business process

Scenario: Trigger a monthly salary review on the first day of each month.

User: "Schedule the salary review workflow to run on the first day of every month at 9 AM"

Result: The schedule:

  • Runs the salary review workflow.
  • Runs on the first day of each month at 9:00 AM.
  • Prompts managers for feedback.
  • Continues monthly with no execution limit.