Skip to content
Note

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

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.

Earns Its Keep

Every Sunday, one post on Dataverse, .NET, and whether the tools we rely on still deserve to be there.