How do you persist cloud-worker output before the process exits?

How do you persist cloud-worker output before the process exits?

A worker’s working directory should not be the only copy of a completed video. Cloud execution instances can end, restart, or be replaced.

Use a controlled workspace

Create per-attempt paths to avoid collisions between jobs. Download required inputs, render, and validate output within that workspace. Bound temporary-file growth and clean up when an attempt ends. Do not use a developer machine path as a production artifact location.

Commit the durable result

Upload the validated output to the intended storage key, verify it, and update the job’s canonical result reference. Handle a failed database update after upload through repeatable finalization. Only then report application completion. Test termination after rendering but before upload, and after upload but before state update. Those boundaries reveal whether retries can recover without losing or duplicating the final artifact.