Every so often we get a failed deployment that has the line couldn't update ENVs for /xxx/yyy (where /xxx/yyy is a random functions URL)

the next deployment will usually succeed with no changes to the code in that function, or sometimes fail with the same message for a totally different function

so it seems random and non-deterministic.

We'll check this.

This issue is a rare one and it can happens when two or more deployments are running at the same time. We need to add a queue here eventually but for now, try to only deploy one at a time and this issue should not occure.

@sheena could you confirm that sometimes you push a commit and then a few seconds later do another one and push as well?