Scheduler

Run jobs on a schedule: a weekly summary email, a nightly cleanup, a one-shot reminder. SQL jobs run inside your Wok's Postgres via pg_cron. Work that needs an external API or model runs in an Edge Function invoked by TellWang's scheduler.

Schedule a job

The control plane exposes scheduler CRUD over the same Bearer auth as the rest of your Wok: list jobs, create one (cron expression + SQL or recurring Edge Function), update, or delete. Recurring function runs enter the durable invocation queue, run one at a time per Wok, and coalesce missed ticks while the same schedule is pending or running. Requests receive a fresh service-role credential for that Wok; no bearer token is stored in the schedule body.

Schedule weekly-summary to run every Monday at 09:00
on my Wok.

Run once at a future time

Use schedule_function_once, or lollipop schedule-function-once in an Agent Cell or terminal, for an exact future RFC3339 timestamp. Use list_function_invocations or lollipop list-function-invocations to inspect attempts and the final result.

An edge function can also post {function_name, run_at, payload, idempotency_key} to its injected TELLWANG_FUNCTION_SCHEDULE_URL using SUPABASE_SERVICE_ROLE_KEY. Due work is checked once per second, leased across restarts, limited to one running invocation per Wok, and never starts before run_at. Ordinary failures retry up to three times. A 90-second wall-clock or equivalent supervisor cancellation fails terminally with CP_FUNCTION_INVOCATION_WALL_CLOCK. Delivery is otherwise at least once, so targets must deduplicate non-repeatable side effects.

Good for

• A weekly or daily summary email.
• Nightly cleanups (expire old rows, archive files).
• Reminders and follow-ups.

See what ran

Every run is recorded in your own database. Query cron.job_run_details for what fired, when, how long it took, and whether it succeeded.