Concurrent deployment builds can trigger OAuth errors leading to repository connection being disconnected

[jamesmacwhite]

This has been a problem for a bit of time now, but there is a race condition with deployments that if you have concurrent builds occur, it is possible to cause invalidation on the OAuth token due to multiple API calls within a certain window triggering one API request to be valid but then causing further API calls to be invalid which then drops the repository connection entirely.

#96 potentially identifies a blindspot regarding this issue, although ideally the general bug should be addressed. Even if disabling concurrent builds is a solution that is better than the current situation.

[jamesmacwhite]

A workaround is ensuring each Craft Cloud project is pointing to a separate branch. We had two environments using develop and then one to main, the issue is concurrent deployments triggered by on-push, would cause OAuth token issues.

There might still be a way to trigger this, but with enough gap between a deployment between multiple environments it should mitigate it.

[timkelty]

Thanks for the post @jamesmacwhite.

Resolving the integrations/oauth issues is on the top of our priority list.

[angrybrad]

The original concurrency issue posted should be resolved now.