Thank you for your response! We are on AWS rather than Azure, and (as a result?) the error messages do not seem to match those in the article you provide. We have tried some of the suggestions anyways, such as removing external maven libraries, to no avail.

Switching to pools has mostly reduced the issue, but when new clusters are needed because the pool clusters are already in use, we occasionally receive the original error still.