Changelog
Product updates, new features, and improvements to Recuro.
Every outgoing HTTP request can now be signed with HMAC-SHA256. Enable signing on a cron or job, and Recuro attaches a signature header your endpoint can verify. No more guessing whether a request actually came from your scheduler.
Define what “success” means beyond a 2xx status code. Assert on response body content, specific status codes, or header values. If the assertion fails, Recuro treats the execution as a failure and triggers retries and alerts accordingly.
Cron expressions now run in the timezone you choose. Set America/New_York, Europe/London, or any IANA timezone on a cron schedule. No more mental UTC offset math.
Recuro now ships an MCP server. Connect it to Claude Code, Cursor, Windsurf, or any MCP-compatible client to manage crons and jobs from your editor. Create schedules, list executions, and check failure history without switching to the dashboard.
Jobs that exhaust all retry attempts now land in a dead letter queue instead of disappearing. Inspect failed payloads, understand what went wrong, and replay them when you’re ready.
Get notified when a job finishes. Set a callback URL on a queue and Recuro will POST the execution result (status, response, duration) to your endpoint after each job completes — success or failure.
Control how many jobs in a queue run concurrently. Set a parallelism limit to prevent overwhelming downstream services, or leave it unlimited for maximum throughput.
Set a failure threshold on any queue. After consecutive failures hit the threshold, Recuro sends an email alert. When things recover, you get a recovery notification automatically.
Both the Crons and Jobs dashboards now show a stats bar with total counts, active/paused breakdown, and failure rates at a glance. The Jobs view adds a URL column, execution duration, and search. The Crons view shows last run time and URL tooltips on hover.
The /api/jobs endpoint lets you push one-off or delayed HTTP jobs to named queues programmatically. Each job carries its own URL, method, headers, and payload. Queues are created automatically by name if they don’t exist yet.
Create HTTP cron jobs with any standard cron expression. Set the URL, method, headers, and payload. Recuro calls your endpoint on schedule with automatic retries on failure.
Push one-off HTTP jobs to named queues. Each queue has its own retry policy and timeout settings. Jobs execute in order with configurable retry attempts and exponential backoff.
See response times, success rates, and execution history for every cron and job. Filter by status, search by URL, and inspect individual request/response details.
Invite team members and manage access. Admins control membership, all members get full access to crons, jobs, and execution history within the team.