So the past couple of BC 365 SaaS version updates have resulted in my sandbox environments lagging when it comes to pushing AL code updates via VS Code. After five minutes, finally it times out. With the reported error -- /...failed with code UnprocessableEntity. Reason: We can't save your changes right now, because the data is being updated in a transaction done by another session./ I restarted my target sandbox environment and then I was able to push my AL code updates fine. Then after some more code revisions, my next attempt to push them resulted in the same timeout. And I'm the only user in the entire tenant. There are no other active or inactive user sessions. And the version updates already completed over 6 hours ago.
Is this going to be standard operating procedure over the long haul? What's strange is the sandbox environment that fell into this was already at the latest version (22.2.56969.57282). The reason why is because I had to create this new sandbox environment after the previous one locked up due to this same thing after the previous version update. I get it, in that I can wait a day or two and try pushing my AL code updates again. Not the most effective working scenario when it comes to completing projects and whatnot.
583
Share
Report
All responses (
Answers (
