Cron that survives deploys and tells you what ran.

In-process timers die with the process. Serverless crons run with no history and no retries.

Start building Read the docs

Schedule stored

test

Nightly reconciliation

sch_2d71 · 0 2 * * * · Europe/Berlin

Active

target: POST /reconcile
missed ticks: skip, not backfill

Occurrences

Not an in-process timer. The schedule survives deploys and restarts. Next fire: 02:00.

How Flowyn handles it

What you get instead of building it.

Durable schedule

A cron expression and a timezone, stored by Flowyn.

Ordinary jobs

Each occurrence creates a durable HTTP job with its own attempts and retries.

Skip, not backfill

Missed occurrences are skipped so a long outage does not cause a storm.

Inspectable history

Every occurrence and every attempt can be read back.

API example

A real request against the Flowyn REST API.

Full request and response contracts are in the docs.

Limits worth knowing

Five-field cron, so the minimum interval is one minute
Missed occurrences are skipped, not backfilled
Jobs use the schedule's timeout and attempt budget

POSThttps://api.flowyn.dev/v1/jobs202

curl -X POST https://api.flowyn.dev/v1/jobs \
  -H "Authorization: Bearer flw_test_••••" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: sync-invoice-881" \
  -d '{
    "url": "https://api.example.com/reports/generate",
    "method": "POST",
    "timeout_ms": 10000,
    "max_attempts": 5
  }'