Manage scheduled triggers
A scheduled trigger is work that waits for a time and then does one thing. Recurring work is expressed this way rather than as a task somebody remembers to re-create.
This page uses SUM-17, the weekly refresh of the Summitline trail-conditions feed.
What one holds
Section titled “What one holds”- A trigger time, when it fires.
- An action, one of four kinds: publish something, invoke a tool, transition another task’s state, or emit an event other work reacts to.
SUM-17emits an event: refresh the ranger district conditions.
The lifecycle
Section titled “The lifecycle”| State | Means |
|---|---|
| waiting | Counting down |
| fired | The time arrived and the action ran |
| cancelled | Called off before it fired, with a reason |
The workspace shows the state as a pill next to a countdown: time remaining while it waits, and when it fired afterwards.
Find every trigger
Section titled “Find every trigger”The task list is the management view. On the Tasks page open Filters and set Type to Scheduled Trigger, or go straight to /app/tasks?taskType=scheduled_trigger. The list switches to All automatically, because scheduled work is rarely assigned to you personally.
Cancel one
Section titled “Cancel one”-
Open the trigger and select Cancel trigger.
-
Write the reason. It is required, and it is stored on the task.
-
Confirm with Cancel trigger, or back out with Keep trigger.
Cancelling only affects the trigger. Whatever created it decides what to do next: a content task whose publish trigger is cancelled stays where it is rather than advancing to measuring, so cancel the trigger when you want to hold a publication, and kill the content task when you want to drop the piece.
A trigger that has already fired cannot be cancelled. It is a record of something that happened.
Creating one
Section titled “Creating one”+ New ▾, then Scheduled Trigger, on the Tasks page. Most triggers are created by the work that needs them: a content task entering scheduling creates its own, with the publish time the calendar chose.
Next steps
Section titled “Next steps”- Run a content task: the pipeline that schedules publication.
- Move a task through its statuses: the lifecycle ordinary tasks use instead.
- Task types: the five specialized types side by side.