Views:

Applies to Product - Microsoft Dataverse



What’s happening?

The customer is experiencing issues with deactivated workflow triggers still appearing in the system jobs, despite being marked as deactivated.


Reason:
The underlying cause is related to the behavior of workflow definitions and activations. When a workflow is created, a workflow definition is established. Deactivating a workflow does not delete the workflow activation, which represents a snapshot of the workflow definition at the time of activation. The activation remains until all system references to it have been cleaned up.


Resolution:

  1. Deactivate the workflow in the source environment.
  2. Import the deactivated workflow to the target environment.
  3. Attempt to reproduce this again.
  4. If the workflow is still triggering, verify that the correct filtering is applied to see only the relevant entries, such as filtering by type equals to definition.
  5. Note that the activation will remain for a period of time after deletion of the workflow definition, until all references are cleaned up through a recurring daily bulk delete job.
If this persists after following these steps, further investigation may be required.