Dataverse - Synapse change files not merged anymore

Welcome to Microsoft Q&A!

@Steven Bogaers I hope you are doing well,

Building on Himaja's excellent points, it looks like the background metadata processor got caught in a persistent retry loop during your previous capacity outage and is now failing to recover on its own (as indicated by the 102 attempts and TableMetadataUpdated: false).

Because the change files are still arriving at the storage account, the upstream connection is fine, but the downstream merge process is blocked waiting for that metadata flag to clear.

Recommended Next Step: To break this loop and force the metadata to update without waiting on a backend support ticket, the most effective self-service workaround is to remove and re-add the affected tables in your Synapse Link profile:

Go to the Power Apps Maker Portal (make.powerapps.com) and navigate to Azure Synapse Link.

Select your active link profile and remove the specific F&O tables that are stuck.

1. Save the profile, wait a few minutes for the backend to clear the blocked state, and then re-add the tables.

This process will force the system to perform a fresh initial sync for those specific tables, completely regenerating the metadata and allowing the change files to start merging again.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution

Hi @Steven Bogaers ,

Thank you for reaching out to the Microsoft Q&A forum. 

This looks like the metadata synchronization process is stuck after the D365 F&O database capacity issue.

The important status values are:

TableMetadataUpdated: false

IsCompleted: false

IsSynapseArtifactsUpdateInvoked: false

NoOfAttempts: 102

The fact that new change files are still being created means the data changes are reaching the storage account, but the downstream Synapse merge/metadata processing is not completing.

I recommend the following:

Confirm that the D365 F&O database capacity issue is fully resolved and there are no ongoing capacity or throttling errors.

Check the Synapse Link monitoring/logs for errors around DataSyncMetadataProcessor.GetAllMetadataForEntitiesFromCRM.

Check whether the issue affects all tables or only specific tables.

Verify that the Synapse workspace and storage account have sufficient capacity and that the required permissions are working.

Do not manually delete or merge the change files, as this may cause data synchronization issues.

Since the process has already made 102 attempts and has been stuck for around three weeks, if there is no actionable error, I recommend opening a Microsoft support request for further investigation of the metadata synchronization state.

The main point is: change files are being generated, but the metadata update/merge stage appears to be stuck. The error from GetAllMetadataForEntitiesFromCRM would be the most useful information to identify the exact cause.