Views:

Applies to Product - Microsoft Dataverse
 

What’s happening?
Customers are unable to manage system jobs that are owned by users who are no longer licensed or active. These system jobs are stuck in a waiting state, and the current owners lack the required permissions to execute them.
 

Reason:
The inability to change the owner of system jobs is due to the current owner being inactive. System administrators are also unable to assign these jobs to themselves or others, as there are no workflows, plugins, or business rules affecting those system jobs.
 

Resolution:

  1. Change the workflow owner first. This will allow all new jobs to be triggered in the context of the new owner.
  2. Once the workflow owner is changed, the customer can cancel the existing jobs that are stuck in a waiting state.
  3. The only operations available on these jobs are to pause, cancel, resume, or postpone. There is no option to change the owner of already triggered jobs.
  4. For any system jobs that do not have active users, it is recommended to cancel them and create new identical replacements for the new owner.