A new database version caused a configuration mismatch that has since been optimized. The issue was related to retryable writes at the database level, with an issue causing retries with the same transaction ID to be handled in the same database session. We have deployed a fix which has completely resolved the issue.