Video transcoding jobs

When a source file needs converting, the agent submits it to Rendi with the FFmpeg command your rules define, then reads the job as it runs. It applies your output rules for format, resolution, and bitrate, and updates the job record with the result and a link to the finished file. Jobs that complete within limits post back automatically. A job that fails, runs past a time cap you set, or returns a file that misses your spec is held and escalated to an engineer, who inspects the command and inputs before the clip is used downstream.

Job status handling

Across running Rendi jobs, the agent reads each job status and any error the API returns. It matches the state to your rules, updates the tracking record, and notifies the owner when a job queues, finishes, or errors. Jobs moving through normally update on their own and are logged. A job stuck in progress past your expected window, repeated failures on the same input, or an error the rules do not recognize is raised to an engineer with the job details, so a stalled or looping task gets a human decision instead of silently holding up a pipeline.

Output file placement

Once a Rendi job finishes, the agent reads the output location and moves the rendered file to where it belongs, whether storage, a CMS, or a review folder, per your placement rules. It updates the linked record with the new file and notifies the requester that the media is ready. Standard placements complete automatically and are noted. A missing destination, a file larger than the target allows, or a naming clash with existing media is held and routed to a producer, who settles the placement before the file is published or sent to a viewer.