Skip to main content
A pipeline is an ordered list of task names submitted to the queue as a single job. Tasks run sequentially against the output of the previous step.

Submission shape

Submitted to POST /push.

Fields

Example pipelines

FDX → validated ScreenJSON

ScreenJSON → multi-format ZIP

Convert from Fountain, encrypt for distribution

How it runs

  1. A worker claims the job from Redis (REDIS_INPUT_QUEUE).
  2. It downloads input_key from object storage.
  3. For each task in order, it invokes greenlight.<handler> against the current working file. Outputs land in {output_key}/{task.output_dir}/{stem}.{ext}.
  4. Results are written to REDIS_RESULTS_QUEUE with TTL REDIS_RESULTS_TTL hours.
  5. Webhooks fire (per-job and defaults).
  6. Notifications fan out to any configured drivers.
Failed tasks abort the pipeline; outputs already written stay in place.

Status and results

Track progress with: