BUILD_ID Availability in Deploy Notification Webhook

[fool]

Hiya @lilbigwheel and sorry to be slow to get back to you!

This thread describes the chunking dilemma and some workarounds:

[Support Guide] Why do I see “Uncaught SyntaxError: Unexpected token <” errors? How can I use chunking or versioning for my assets at Netlify?

Last reviewed by Netlify Support on December 2022 The error Uncaught SyntaxError: Unexpected token < is most commonly caused by your site’s code referring to an asset that is no longer available. Most commonly, this is due to a filename change in assets generated during your build. The same situation happens if you use versioned or chunked javascript where the filename changes with every deploy. Let’s look at an example: A file that was named /assets/main-123abc.js would change to /assets…

The webhook notification body (for a completed build) from us around a build should contain all kinds of unique identifiers including the deploy ID and site ID in the JSON - are you not seeing that?

The flow you describe doesn’t sound totally weird but is a bit roundabout - I think I would just use a static version.txt file and check that when a chunked resource 404’s, and force a hard reload in case of that 404.

Or…maybe not use chunks since that simplifies things? Not sure if that is practical for your app.

Re: triggering outgoing webhook without building, only the failed build ones, I guess. You could potentially replay the contents of an old hook with small modifications, using postman or a similar tool, I suppose?