Microsoft Dynamics 365 | Integration, Dataverse...

Archiving data using Dataverse long-term retention stuck in the 'Pending move to history' state.

(3) Share

Report

Posted on by CU06061003-0

Hello Everyone,

I'm working on archiving data using Dataverse long-term retention. I've completed all the prerequisites and setup, and I've scheduled the archival job for inventory transactions. However, the job is stuck in the 'Pending move to history' state. Can someone please guide me on how to proceed?

Categories:

Dynamics 365 general

Power Platform integration

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Adis 6,069 Super User 2025 Season 2 on at

Like (0)

Report
Hi,

I think I read somewhere that it can take up to 2 weeks until this finishes. I did the same for tax transactions and it worked well within few days.

My questions:

If this is done in sandbox, did you release anything there? New custom code, new version update? Did you do a database copy from PROD to UAT

If you can answer the above questions with NO, I would suggest creating a MS Ticket. As far as I know, there isnt much you can do here, like cancelling the job or so.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No
CU06061003-0 21 on at

Like (0)

Report

Hi @Adis,

Thank You for the reply

This was a test environment, and aside from a PQU and a standard Microsoft serivce update, the environment did not have any new custom code or database copy.

The process is still running and struck at pending move to history state.Does the standard update also impact the process?

Was this reply helpful? Yes No
Suggested answer

Adis 6,069 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

If you did updates during this process, then I am pretty sure this is what caused the issue. I would always wait until the process is finished and then do updates, no matter if it is a Microsoft update or you are releasing custom code.

I would make a database copy from PROD to your test environment and start the process again. I am pretty sure it will run through with no issues.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No
CU06061003-0 21 on at

Like (0)

Report

Hi @Adis,

Thank You for the response.

What would happen if the same situation happened in production environments and the job was interrupted at one point or another? How do we handle it?

Regarding situations of similar kind Is there documentation on this topic in any of the MS docs or other related documents? Please let me know if there are, it would be very helpful.

Best regards,

A seeker in need of assistance

Was this reply helpful? Yes No
Adis 6,069 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

If that happens in PROD I would suggest to create a MS ticket so they help you to resolve the issue. In order to avoid such a situation, I would make sure to prevent making updates during the archiving.

I guess someone will still do it and MS will need to fix it at some point of time, however, I would try to avoid it as of now.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No