Something to consider is that on our CDN:
- if we for instance upped the time limit for your site’s function runs
- but you hadn’t redeployed the
devbranch successfully since we made the change - then it could be using the older, non-increased-timeout config.
We say “redeploy your site” to update the config, but we actually mean “redeploy each context”. So, this operation may have replaced an older deploy with a less accommodating config.
Or not - hard for me to know without more details, just speaking to what I could think of that might have caused this.