Engine room, event types, travellers and executions

Watching the background engine — the queue of scheduled work, what each event type does, and where to look when something did not happen.

Everything that happens later — a delayed email, a scheduled post, an agent working a task, a newsletter batch, a nightly meter — is an event in a queue that the engine drains every minute.

Engine room

/engine shows the queue live: pending, running, done and failed counts, and the events themselves with type, what they belong to, when they are due and their result. Filter by type with the pills. A failed event shows its error.

Event types

/cron-types lists every kind of event with a 24-hour tally per type. Among them: Agent task, Flow run, Traveller resume, Creator tick, Newsletter send / A/B decide / stats refresh, SMM post, Subscription billing, Cart recovery, Affiliate period advance, Member status expiry, Mail poll, Product expiry reminder, Storage credits meter, Model catalog sync, Flow schedule sweep.

Travellers

/travellers — every run in flight: which flow, which step, waiting for what, the data it carries, and the log of what it has done. Resume or end one by hand if you need to.

Executions

/executions — the history of finished runs, step by step. Open one to see the data at each step and any error.

When something did not happen

1. Find the traveller or execution and read where it stopped.
2. Check the engine room for a failed event of the matching type.
3. If the event is pending but past due, the engine has not reached it yet — it will.