CONTENT CREATION

Render teasers from an S3 still drop with retry and failure escalation

Fires when a still is uploaded to an S3 bucket, renders a watermarked teaser via Replicate with an automatic retry, archives the finished clip back to S3.

CategoryContent Creation
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew still uploaded to S3 prefixAWS S3
  • ActionRender teaser clip with ReplicateReplicateReplicate
  • LogicBranch on render result; retry on transient failure
  • ActionComposite watermark onto videoImage generation
  • OutputArchive finished clip back to S3AWS S3
  • ActionOpen PagerDuty incident if render keeps failingPagerDutyPagerDuty

What it does

A production-grade renderer for high-volume still drops: it animates each new S3 upload into a watermarked teaser, retries transient render failures, archives the output, and escalates a hard failure so nothing silently disappears.

When to use it

Use when teaser rendering is part of a larger automated pipeline feeding from object storage and reliability matters more than a human-in-the-loop step. Best for teams running many renders a day who need failures surfaced, not buried.

How it works

  1. 1A new object in the watched S3 stills prefix triggers the run.
  2. 2The still is sent to Replicate's image-to-video model to render a teaser clip.
  3. 3A branch inspects the render result: success continues, transient failure retries once.
  4. 4On success, the brand watermark is composited onto the video.
  5. 5The finished clip is archived to the S3 outputs prefix with metadata.
  6. 6If the render still fails after retry, a PagerDuty incident is opened with the asset reference for the on-call operator.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AWS S3Buckets, objects, signed URLs.
  2. 2
    Connect ReplicateImage, video, and model inference.
  3. 3
    Connect Image generationManaged Nano Banana image renders, metered per image.
  4. 4
    Connect PagerDutyIncidents, on-call, escalations.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.