web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Workflow Stuck at Waiting Status

(0) ShareShare
ReportReport
Posted on by 1,788

We have a workflow that runs as a background process. We have recently noticed that we have a lot of these processes seemingly stuck with the status of Waiting. If I select the process and choose Resume, it appears to run but the task it is performing is not completed.

 

How can I troubleshoot this?

*This post is locked for comments

I have the same question (0)
  • MDS Profile Picture
    1,788 on at
    RE: Workflow Stuck at Waiting Status

    Further investigation suggests it's a permissions error. How can I tell what user the process is running as? I can see the process owner - is it one in the same? If so, I would presume the owner will need a CRM licence?

  • Suggested answer
    Community Member Profile Picture
    on at
    RE: Workflow Stuck at Waiting Status

    it Hapened to me, you're using online version right?

    if yes, contact microsoft because it's probably an error in their servers, that stuck you processes, I did it, and they solved.

    If you're using on-prem version, the same, the problem is with you server.

    I hope it helps you.

  • MDS Profile Picture
    1,788 on at
    RE: Workflow Stuck at Waiting Status

    I think it's more than likely related to the workflow owner. The owner of mine had his CRM licence revoked so presumably the process (automatic background process) could no be authenticated against the record it was updating.

    What is the best way around this? Do I need to change the ownership of the processes to be that of a current CRM user (with required privilges)?

  • Suggested answer
    Sean Michel Profile Picture
    340 on at
    RE: Workflow Stuck at Waiting Status

    Hi MDS,

    It depends on your goal for the Workflow, and your security set-up.

    If the Workflow is synchronous, and set to run as the Owner of the Workflow, and you don't need to capture the User who ran the workflow for any reason, you'll want to assign the Workflow (Actions > Assign) to a System Administrator.

    Otherwise, if you have no security limitations that you need System Admin to bypass, you can set the workflow to run as the "User who made changes to the record", and the workflow should run under the initiating User's context. In this scenario, you should still change the owner of the Workflow to a System Admin, to prevent lic. issues in the future.

    Finally, if you're not running this as a synchronous workflow, you'll just need to assign the Workflow to a System Administrator (this ensures no privilege issue), and it will execute accordingly.

    To answer your question - the Owner of the workflow WILL need a valid CRM lic, so that should be the root of your issue.

    Let me know if you have further questions!

  • Suggested answer
    MDS Profile Picture
    1,788 on at
    RE: Workflow Stuck at Waiting Status

    Hi Sean,

    Thanks for your reply - that's really useful.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
HR-09070029-0 Profile Picture

HR-09070029-0 2

#1
UllrSki Profile Picture

UllrSki 2

#3
ED-30091530-0 Profile Picture

ED-30091530-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans