Skip to content

Jobs & Workers

Long-running tasks in CRAFT Studio run as background jobs so the UI stays responsive. Jobs are channel-scoped and — except for a handful of always-on tasks like TTS and resource downloads — premium-only.

Opening the Jobs panel

Click the channel pill in the top chrome, then Jobs in the dropdown. The entry only appears for premium users (admin auto-qualifies — see Roles).

What runs as a job

JobWhat it does
OrchestrateDrives the 8-stage Episode pipeline with quality gates and feedback loops
IdeaAI idea generation in character voice
ProposalsAI-scored proposals with trend analysis
Fact-checkClaim verification across the script
HumanizeDetect and rewrite AI-sounding passages
TTSText-to-speech rendering and merge
DiscoverYouTube research (yt-dlp) with progressive filtering
Resource downloadPull assets from the 14 sources
RenderRemotion → MP4 export (Chromium)

Lifecycle

Every job goes through the same four states you'll see in the panel:

  1. Queued — submitted, waiting for a worker slot.
  2. Running — a worker picked it up; progress streams live over server-sent events.
  3. Completed — success; result is persisted (e.g. new script, rendered MP4).
  4. Failed — error captured; failed jobs retry automatically up to three times before requiring manual intervention.

Each job row expands to show streamed output, duration, and (where applicable) a link to the produced artifact.

Cancellation

Any running job can be cancelled from its row. Multi-stage jobs (the 8-stage pipeline) stop cleanly at the next stage boundary so they don't leave half-finished artifacts behind.

Why jobs?

Running work off the main request path means:

  • The studio stays interactive while a 20-minute video renders.
  • Failures are recoverable — the job can retry, be cancelled, or kicked off again with tweaked inputs.
  • Long pipelines (Episodes) can span hours without timing out anything.

Real-time updates

While a job is running, its progress appears in two places:

  • The Jobs panel — live-streamed output, stage updates, and status chips.
  • The panel that initiated it — e.g. a streaming script appears in the editor as the model writes it; a generated image appears in the gallery the moment it's ready.