How to cancel / delete System Batch Jobs?

(6) Share

Report

Posted on by Johnny

6,494

Hi,

There is a "Data cache refresh batch" system batch job, which is stuck in Executing and we can't cancel it.

It does not do anything, there is no Batch Job History. So it is just stuck in executing mode and we can't even create new Job.

If we try to do Change Status >> Canceling, it throws error "System task status cannot be changed".

If we click Remove reccurance, nothing happens.

If we go to Reccurance and set it to "End after 1", it throws "System Job with job id: xxx and end datetime: should be scheduled to run at least once every 7 day(s)".

If I go to batch tasks, the "Abort" button is greyed out.

I could not find anything helpfull online.

Any ideas?

Thanks

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Subra 1,247 on at

Like (0)

Report
Copy link

Link copied!

Hi

How long the batch has been in executing status?

Was this reply helpful? Yes No
Verified answer

Alireza Eshaghzadeh 15,200 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hi @Johnny

The message “System task status cannot be changed” is expected in this case because “Data cache refresh batch” is a system batch job. Microsoft Learn also mentions that system jobs can’t be cancelled in the same way as normal user-created batch jobs.

This batch job is related to the data cache framework (SysDataCacheRefreshServiceV2 class) used for workspace tiles/lists. In many environments, this job can appear as Executing because it is designed to keep the cache updated. So first I would confirm whether it is really stuck or just continuously running by design.

Was this reply helpful? Yes No
Suggested answer

Shaluma 137 on at

Like (1)

Report
Copy link

Link copied!
Hi John,
To help resolve batch jobs that are stuck in the Executing status, you can try the following steps:

For Microsoft-hosted environments

Open Environment monitoring in the Lifecycle Services (LCS) environment.

Temporarily disable batch processing.

Re-enable batch processing after a few moments.

For Tier-1 / Development environments

Restart IIS.

Restart the Batch service/AOS.

In many cases, restarting the batch server clears stuck batch records. Similar issues in AX/D365 environments have often been resolved by restarting the batch AOS before attempting to reset job statuses.

Additional maintenance steps

Navigate to System administration > Periodic tasks > Batch job history clean-up.

Run the clean-up process, if available.

Restart batch processing from the application

Go to System administration > Setup > Server configuration.

Disable batch processing for the active batch server and save the changes.

Re-enable batch processing and save again.

Verify whether the affected batch job moves out of the Executing status.

If the issue started after a deployment or metadata change

You may also want to perform a cache refresh by running the following URL:

https://<yourenvironment>.operations.dynamics.com/?mi=SysClassRunner&cls=SysFlushData https://<yourenvironment>.operations.dynamics.com/?mi=sysclassrunner&cls=sysflushaod
https://<yourenvironment>.operations.dynamics.com/?mi=sysclassrunner&cls=sysflushdictionary

This refreshes the application-layer cache and can help resolve issues related to metadata or deployment changes.

Please let us know the outcome after completing these steps, and we can assist further if the issue persists.

If nothing works
Please raise a Microsoft support ticket and provide:
In most cases I've seen, Microsoft resolves this by clearing or resetting the orphaned batch record in the backend database because system jobs cannot be manually canceled from the UI.

Is this Production, UAT/Sandbox, or Tier-1 Dev VM?
Thanks!
If you found it helpful, please consider marking it as Verified — it may be useful for others in the future!

Was this reply helpful? Yes No
André Arnaud de Cal... 305,643 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi Johnny,

As suggested by Alireza, this batch job is designed to run continuously. You can verify this by looking at the coding of the class for this job.

Was this reply helpful? Yes No
Johnny 6,494 on at

Like (1)

Report
Copy link

Link copied!

Hello @André Arnaud de Calavon @Alireza Eshaghzadeh,

Okay, but in our Prod environment we can actually see that there are records created in Batch-Job history.

In UAT, there are no records in history.

That makes me think that in UAT it is just stuck and does not really do anything.

Also... I just checked, and in PROD there is 10 min reccurance set, in UAT it's 1 min.

Was this reply helpful? Yes No
André Arnaud de Cal... 305,643 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi Johnny,

The scenario from your question seems to be related to the UAT? Was there a database restore done recently?

Was this reply helpful? Yes No
Johnny 6,494 on at

Like (0)

Report
Copy link

Link copied!

Hi @André Arnaud de Calavon

Yes it is UAT.

No, we have this database for at least past 3 years.

Maybe I'll just create MS ticket

Was this reply helpful? Yes No