Fabric Mirrored Database Change Feed Eventstream source connector stuck in a restart loop

Hi philhansen,

Thanks for testing that and for clarifying the support situation.

Since the same failure occurs in a newly created Eventstream containing only the Mirrored Database Change Feed source, I think you have isolated this away from the Filter and Activator. The mirrored database is healthy, Change Feed is enabled, and the minimal reproduction still fails, so this now looks specific to the source connector or its interaction with the Open Mirroring implementation.

I understand your frustration regarding the support route. Because the connector is currently in Preview, it is not covered by the same production guarantees as a generally available feature. Given that your MSP has advised that they cannot raise it through their normal Microsoft support channel, posting a clear reproduction here may currently be the most practical escalation path available to you.

To make the report as actionable as possible for the Fabric team, I would add the following details to the thread, provided none of them expose sensitive information:

• Fabric capacity region
• Eventstream ID and connector ID
• The approximate restart interval
• Relevant runtime-log timestamps
• Confirmation that the issue occurs with a single small table
• Whether all mirrored tables are affected
• Whether the same EXPORT_TIME value is replayed after every restart
• The Open Mirroring metadata format and file-generation pattern being used

You could also verify through the mirrored database definition that enableDeltaChangeDataFeed is stored as true, rather than relying only on the portal setting. That would give Microsoft one more concrete data point and remove another possible configuration question.

At this point, I do not see a documented customer-side fix for this specific validation loop. I would also avoid treating downstream deduplication as the solution, because it may protect the destination from duplicate events but would not resolve the connector repeatedly restarting and replaying its snapshot.

Hopefully someone from the Fabric product team can review the reproduction and runtime details here. Please keep the thread updated if you receive any further information from your MSP or Microsoft.