Skip to main content

Notifications

Announcements

No record found.

Small and medium business | Business Central, N...
Answered

AL Extension upload fails - "failed with code UnprocessableEntity"

Posted on by 7

I have been experiencing an issue in our sandbox development environment. I have been receiving an error message when trying to upload my extension form vscode to a saas sandbox.

Debug console:
The request for path /v2.0/sandbox-development/dev/apps?SchemaUpdateMode=forcesync&IsRad=true&DependencyPublishingOption=default failed with code UnprocessableEntity. Reason: Ihre Änderungen können jetzt nicht gespeichert werden, da die Daten in einer Transaktion aktualisiert werden, die von einer anderen Sitzung ausgeführt wird.
Sie müssen warten, bis die andere Transaktion abgeschlossen ist, was eine Weile dauern kann. Versuchen Sie es später erneut.

The error message I am receiving is in German, and it translates to: "Your changes cannot be saved now because the data is being updated in a transaction being run by another session. You have to wait for the other transaction to complete, which may take a while. Try again later."

But I am completly sure that there is no other process. I did try to restart the enviroment.

I understand that this typically means that another session is using the same data I am trying to manipulate. However, I am certain that no other process is currently active that could be causing this conflict. I have even attempted to restart the environment to clear any possible lingering sessions, but the issue persists.

Could you please provide guidance on this issue? I am interested in understanding whether there could be a hidden or dormant session that is interfering with my process or if there might be a bug or an issue with the system itself that is causing this error.

  • Verified answer
    YUN ZHU Profile Picture
    YUN ZHU 73,696 Super User 2024 Season 2 on at
    RE: AL Extension upload fails - "failed with code UnprocessableEntity"

    Hi, I've encountered the similar problem a few times. Restarting the environment or re-creating Sandbox will temporarily solve the problem, but then it would reappear after a few publishes.
    I think this is usually caused by a sudden slowdown of the SaaS environment, and it usually resolves itself the next day.

    pastedimage1683851303369v1.png

    If it has not been resolved, you can try to use the copy function to recreate the Sandbox.

    pastedimage1683851332617v2.png

    Hope this helps.

    Thanks.

    ZHU

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans