I’m uploading videos via a backend worker service that processes queue jobs—first uploading the file
I’m uploading videos via a backend worker service that processes queue jobs—first uploading the file to R2, then providing the R2 link to Cloudflare Stream’s upload-via-link functionality.
When the video successfully uploads to R2 and starts processing in Cloudflare Stream, sometimes it fails or shows the 424 error. In those cases, I can’t re-trigger the upload-via-link process programmatically from the backend because the upload is already considered “in progress” or partially done and my job is to make the process upto provide the r2 link to cloudflare and its upto cloudflare then it queue, process and ready the video on its own.
So, to recover from this, I have to manually log into the Cloudflare dashboard, go to Stream, and use the upload-via-link option again with the same R2 link to upload the file manually. This manual step is necessary because the full upload-via-link cycle can’t be retried automatically from the code once a failure occurs during processing.
When the video successfully uploads to R2 and starts processing in Cloudflare Stream, sometimes it fails or shows the 424 error. In those cases, I can’t re-trigger the upload-via-link process programmatically from the backend because the upload is already considered “in progress” or partially done and my job is to make the process upto provide the r2 link to cloudflare and its upto cloudflare then it queue, process and ready the video on its own.
So, to recover from this, I have to manually log into the Cloudflare dashboard, go to Stream, and use the upload-via-link option again with the same R2 link to upload the file manually. This manual step is necessary because the full upload-via-link cycle can’t be retried automatically from the code once a failure occurs during processing.
