Edit a trigger#

Editing happens via the same /schedule endpoint. Specify the trigger to update using either ttr-trigger-idheader or ttr-custom-keyheader.

The existing trigger is updated in place with the new schedule time, URL, method, headers, and body. The same flow works for recurring triggers — updating a cron expression, URL, or tag set is just another /schedule call with the matching identifier.

Reschedule by trigger ID#

Pass ttr-trigger-idheader with the ID returned when the trigger was first scheduled.

For one-shot triggers, the trigger must still be in registered state (not yet executed or cancelled). For recurring triggers, the generator must still be active.

The response will have "operation": "reschedule".

Reschedule by custom key#

If you originally provided a ttr-custom-keyheader, any subsequent call to /schedule with the same key will reschedule the existing trigger or generator, as long as it hasn't been executed or cancelled.

This is the recommended approach for idempotent scheduling.

Editing recurring triggers#

Re-POST a cron(...) schedule with the same generator ID or custom key to update a recurring trigger. The currently-pending instance is replaced; past instances keep their original URL, headers, and tags.

You can also flip a trigger between one-shot and recurring: posting cron(...) with the same custom key as an existing one-shot will cancel the one-shot and create a generator owning the key (and vice-versa). See Custom trigger keys.