Product Roadmap#

We're actively developing TimeTriggers. Here's what's on the roadmap, and what shipped recently.

Coming next#

• Webhook signature verification (HMAC)
• Self-hosted agent (Docker container for firing from your own infra)
• Pause / resume all triggers in a project

Recently shipped#

• Recurring triggers. Schedule a trigger that repeats on a cron expression — see Recurring triggers.
• Tag policies. Per-tag throughput limits over rolling windows of up to 30 days (units s, m, h and d, decimal rates allowed), concurrency caps, and request timeouts from 1 to 3600 seconds (300 by default). Manage them with the /tag-policies API or on the dashboard's Tag Policies page — see Tag policies. These replace the fixed per-second through per-month rate limits: there's no week or month unit, and existing per-week and per-month limits became 7d and 30d windows.
• Retry policies. Fixed or exponential backoff per tag, with a maximum number of attempts, a delay cap, optional jitter, and a choice of which failures to retry: network errors only, network errors and 5xx, or any non-2xx response — see Retries. Retries are opt-in: without a retry policy, a failed attempt is final and becomes a dead letter.
• Execution history in the dashboard. The Executions page lists attempts across your triggers, including retries and replays, with filters for trigger ID, custom key, status and HTTP status, plus an Only dead letters toggle. Each trigger's page lists all of its attempts with the response status, headers and the first 10 KB of the body — see Executions and Execution records. This history is in the dashboard only; you can't read it with an API key.
• Manual replay. Replay now / Retry now on a completed trigger in the dashboard queues the trigger's stored request to be sent again, as a new execution — see Replay and retry. Replay is available in the dashboard only, not with an API key.