Outputs larger than 100 MB now complete
Jobs whose result file was over 100 MB used to fail at the final upload step. They now upload the output straight to storage and complete normally.
A job that produced an output file larger than 100 MB used to fail right at the end, after the encode had already run, with an EXECUTION_ERROR about the upload. The output was too big for the size limit on the upload path.
The output now goes straight to object storage instead of through that path, so size is no longer the bottleneck. Large transcodes, long renders, and high-bitrate exports finish and return a downloadable URL like any other job. Smaller outputs are unaffected and take the same fast route as before.
Retention and size limits per plan are under plan limits. Large files also start playing immediately now, see video outputs stream and seek.