Skip to main content
Scheduled tasks let you run automation actions on a fixed cadence, independent of any workspace event. Instead of waiting for a trigger, a scheduled task wakes up at the time you define — every weekday morning, once a week, every few hours — and executes its actions automatically. Use them to send recurring status reports, reset fields at the start of each sprint, or ping a webhook on a regular heartbeat.

​
Creating a scheduled task

1

Open the Automation hub

Navigate to your project or workspace and click Automation in the left sidebar.
2

Go to the Scheduled tab

In the Automation hub, click the Scheduled tab to view all existing scheduled tasks.
3

Create a new scheduled task

Click New in the top-right corner. The scheduled task editor opens.
4

Name your task

Enter a descriptive name so you can identify this task at a glance in the run log (e.g., “Weekly sprint summary to Slack”).
5

Choose a schedule

Select a preset schedule or enter a custom cron expression:
  • Daily — runs once per day at a time you choose
  • Weekly — runs once per week on a day and time you choose
  • Monthly — runs once per month on a date and time you choose
  • Custom (cron) — enter any valid cron expression for full control
See the cron expression reference below for common patterns.
6

Add actions

Click Add action and configure what this task should do when it runs. You can add multiple actions; they execute in order. The same action types available in rules are available here.
7

Save and enable

Click Save. The task is saved in a disabled state. Toggle it to Enabled in the scheduled tasks list to activate it.

​
What actions scheduled tasks can perform

Scheduled tasks support the same action set as event-driven rules:
ActionDescription
Send Slack messagePost a message to a Slack channel or DM at the scheduled time
Assign taskSet or rotate the assignee on a specified task
Update fieldSet a field value on one or more tasks (e.g., reset a counter field)
Trigger webhookSend an HTTP POST request to an external URL with a configurable payload
Start workflowKick off another automation workflow on schedule
Combine Update field with a weekly schedule to automatically clear a “Weekly notes” field every Monday morning, giving your team a clean slate for the new week.

​
Cron expression reference

Use a custom cron expression when the preset schedules don’t match your needs. fsckmsft uses standard 5-field cron syntax: 
┌───── minute (0–59)
│ ┌─── hour (0–23, UTC)
│ │ ┌─ day of month (1–31)
│ │ │ ┌ month (1–12)
│ │ │ │ ┌ day of week (0–7, 0 and 7 = Sunday)
│ │ │ │ │
* * * * *
All cron schedules run in UTC. Convert your local time to UTC when writing expressions to ensure the task fires when you expect it.

​
Common cron patterns

ExpressionMeaning
0 9 * * 1-5Every weekday (Mon–Fri) at 9:00 AM UTC
0 0 * * 0Every Sunday at midnight UTC
0 */6 * * *Every 6 hours (midnight, 6 AM, noon, 6 PM UTC)
0 8 1 * *First day of every month at 8:00 AM UTC
30 17 * * 5Every Friday at 5:30 PM UTC
*/15 * * * *Every 15 minutes
The minimum supported schedule interval is every 15 minutes. Expressions that would fire more frequently than once every 15 minutes are rejected at save time.

​
Viewing run history

Every execution of a scheduled task is logged with a full record of what happened.
1

Open the scheduled task

In the Scheduled tab of the Automation hub, click the task name.
2

Open the Run history tab

Click Run history in the task detail panel. Each row shows the scheduled fire time, actual execution time, and the result of each action.
3

Inspect a run

Click any row to expand it and see the full action log — including any error messages if an action failed.

​
Pausing and resuming a scheduled task

Pause a task to prevent it from running without deleting it or losing your configuration.
  1. In the Scheduled tab, find the task in the list.
  2. Click the toggle in the Status column to switch it from Enabled to Paused.
  3. To resume, click the toggle again. The task will next fire at the following scheduled time after you re-enable it — it does not run a catch-up execution for the period it was paused.

​
Error notifications

If a scheduled task’s action fails (for example, a webhook returns a non-2xx response or Slack credentials have expired), fsckmsft:
  1. Logs the error in the run history with the full error message and HTTP response code.
  2. Sends an in-app notification to the task’s creator.
  3. After 3 consecutive failures, sends an email notification to the task creator and automatically pauses the task to prevent further failed attempts.
A paused-due-to-errors task will not resume automatically. Review the error in run history, fix the underlying issue (e.g., reconnect your Slack integration), then manually re-enable the task.

​
FAQs

Yes. Open the task detail view and click Run now to trigger an immediate execution. This counts as a real run and is logged in run history, but it does not affect the next scheduled fire time.
Yes. fsckmsft runs scheduled tasks in parallel. Two tasks scheduled for the same cron time will both fire without one blocking the other, though very brief delays (under a second) are possible under high load.
Scheduled tasks can be created at either scope. Tasks created from within a project default to that project’s context. Tasks created from the workspace-level Automation hub run in the workspace context and can act across multiple projects.
The action fails gracefully and logs a “resource not found” error in run history. The task is not automatically paused for a single failure of this type — you’ll receive the usual error notifications after 3 consecutive failures.