Triggers and replay

Replay a request

From Logs or Traffic, any request can be replayed: edit its method, path, headers and body, send it, and see the response. Replays only go to the local dev server (loopback), never anywhere else.

Cron triggers

The Overview’s Triggers section lists the project’s cron schedules, e.g. */15 * * * *. Click one to run scheduled() on the running dev server now, through Miniflare’s /cdn-cgi/local/scheduled. Other cron fires any expression you type.

Queue batches

For a queue consumer, click the queue’s button under Triggers, then Deliver in “Send a batch to queue”. The messages go to its queue() handler, and Flarebox shows workerd’s acks and retries.

This runs with the dev server stopped: Flarebox starts a short-lived instance on the project’s own wrangler and local state, after taking a snapshot. It needs wrangler installed in the project (npm i -D wrangler).