Deployment job not found. - Job Id : 00000000-0000-0000-0000-000000000000

(5) Share

Report

Posted on by AA-24021634-0

Hi,

I’m getting the following error when uploading an extension:

“Deployment job not found. - Job Id : 00000000-0000-0000-0000-000000000000”

Does anyone know:

Why this happens
How to fix it

It looks like the system is trying to reference a deployment job that was never created, is missing, or has an invalid/empty Job ID.

Any guidance would be appreciated.

Thanks.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (12)

Answers (1)

Sort by

Subra 1,247 on at

Like (1)

Report
Copy link

Link copied!

Hi @AA-24021634-0

Where you are trying to upload the extension and let us know which product you have using in Dynamics 365.

Was this reply helpful? Yes No
AA-24021634-0 41 on at

Like (1)

Report
Copy link

Link copied!

Hello @Subra

Yes, I was trying to upload an extension to Business Central.

Was this reply helpful? Yes No
Subra 1,247 on at

Like (1)

Report
Copy link

Link copied!

Hi @AA-24021634-0

Pelase move this question from this forum into Business central forum.

Was this reply helpful? Yes No
AA-24021634-0 41 on at

Like (0)

Report
Copy link

Link copied!

Hi @Subra,

Done, thank you.

Was this reply helpful? Yes No
Suggested answer

Teagen Boll 3,187 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

This might be an AL code error and not your data in BC. I'd try the following.

1. Go to Extension Management in BC and see if any extensions are currently installing or uninstalling.

2. In the D365 Admin Center for BC you can always "Refresh" the sandbox you are using.

3. In VSCode make sure to clear your credentials cache and then download symbols and then publish.

You may want to check for any dependant extensions as well.

Best,

Teagen Boll

Work: Catapult ERP

Social: LinkedIn

Was this reply helpful? Yes No
AA-24021634-0 41 on at

Like (1)

Report
Copy link

Link copied!

Hi,

I already did that and the issue persists.
This is in a SAAS environment.

Best regards,
Angel

Was this reply helpful? Yes No
Verified answer

Grigorios Mavrogeorgis 2,510 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

I have hit this one before. Usually it is the platform not actually queuing the deployment job on backend, so the system points to an empty GUID. Most of the time a page refresh and a retry of the upload after few minutes fixes it, the tenant was probably busy with something. If it keeps repeating, check the .app target runtime version matches the BC version of the environment. When target runtime is higher than the platform it sometimes fail like this instead of giving you a clean version error.

Other thing to check is your permissions, depending on where you upload from you need SUPER inside BC or extension-management related permissions on Admin Center side, otherwise it may fail before a proper deployment job is visible. Look in Admin Center, Environments, then Operations log, usually you will see no job entry at all for that upload. Sandbox or production?

hope this helps.

✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.

Regards

Gregory Mavrogeorgis

Work: GMSOFT Limited
Blog: Inside Business Central
LinkedIn: www.linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No
AA-24021634-0 41 on at

Like (1)

Report
Copy link

Link copied!

Hi,

It is in both Sandbox and Production environment.
I was investigating and found this:

It does work if you repeat it couple of times.

Thanks everyone for the support.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 101,995 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

It seems to be a Microsoft standards issue. Will the same problem occur when uploaded to other environments?
If it's only an issue in this environment, please submit a SR to Microsoft for their assistance in investigating.

Thanks.

ZHU

Was this reply helpful? Yes No
MR-04061010-0 8 on at

Like (1)

Report
Copy link

Link copied!

This is happening to us as well, since tuesday jun 2nd. We have copied our Production env to Sandbox and the app is publish and installed correctly using VS Code and manually as well. We have been uploading other versions before without any problem with our user that has SUPER.

Status: Not Found

We also restored Production environment to a copy on a Production environment not Sandbox and the same behavior is happening.
However, in this new environment if we install the app using sync mode = Force it is installed correctly

We thought that this could work on the actual prod env but it did not:

Haven't heard anything from Microsoft support team. If someone resolved this please advise.

Was this reply helpful? Yes No