My Power Automate flows didn’t trigger after a restore.

by Aug 11, 2025Shorts

My Power Automate flows didn’t trigger after a restore.

Deployed my Dataverse solution from Dev → Acceptance.

Expected instant triggers.

Got… nothing.

And I had a demo in an hour.

Tried: – Off/On ritual (works for printers, right?) – Removed all trigger columns and filters – Blaming the Premium connector licence – “Save As” into a shiny new flow – Even built a new flow from scratch in ACC

Still nothing. No errors. Just silence.

I knew the environment was in Administrative Mode after a restore.

What I didn’t know: There’s a buried setting under administrative mode to enable/disable Background Operations.

After a restore, it was disabled by default. When disabled, Dataverse triggers simply won’t fire.

Enabled background operations → everything worked instantly.

That was a lot of hours wasted on a 1‑minute fix.

Remy van Duijkeren

Remy van Duijkeren

The Marketing Developer

I build automation and integrations that remove the annoying stuff—using Power Platform, Dynamics 365 & Azure.

Get My Thoughts on Automation & Development

Join my personal newsletter and get practical insights on building faster, integrating smarter, and removing friction in IT systems — especially on Power Platform and Dynamics 365.

Related

Hourly billing is nuts.

Hourly billing is nuts. Because the slower someone works, the more you pay. And the faster someone is… the more they get punished. Great system,...

read more