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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

The workflow is not in running state it was completed or cancelled

(3) ShareShare
ReportReport
Posted on by 6
The workflow is not in running state it was completed or cancelled
 
I need to approve orders, and this error appears.
Help please
Picture1.png
Categories:
I have the same question (0)
  • Tom_Gioielli Profile Picture
    2,792 Super User 2025 Season 2 on at
    You're going to need to post significantly more information if you hope to have someone be able to help you with this.
     
    • What product are you approving orders in? Business Central, CE, Powerapps?
    • What is the process and how is it supposed to work?
    • Where did this error come into play, and how was it shown to you (are you trying to review logs, opening a web page to do approvals, or what)?
  • CU16060926-0 Profile Picture
    2 on at

    Hi there,

    This error typically occurs when you're trying to interact with a workflow instance (such as triggering an approval or taking action on a step) after the workflow has already reached a terminal state — meaning it was either completed, canceled, or possibly failed.

    Here are a few things to check and try:

    ✅ 1. Confirm Workflow Status

    Navigate to Advanced Find > Look for Processes > Locate the specific workflow and check its System Jobs:

    • If the workflow shows as Completed, Cancelled, or Failed, it is no longer active and cannot accept further input (like approvals).

    • You’ll need to restart the workflow on the record or create a new instance.

    ✅ 2. Check for Timeout or Exit Conditions

    If the workflow has conditions that could cause it to exit early (e.g., auto-approval logic, missing required data, or a timeout), it may be ending before the approval step is reached. Review the logic in the process designer for conditions that might short-circuit the flow.

    ✅ 3. Use Power Automate Instead (If Applicable)

    If you're using classic workflows and running into limitations, consider migrating the process to Power Automate. It provides better control, logging, and support for wait conditions and approval steps.

    ✅ 4. Re-run or Re-trigger the Workflow

    If this is a test or you're okay reprocessing:


    • Open the affected record.

    • From the ribbon, select Flow > Run Workflow, and choose the workflow again.

    • Ensure the record meets the workflow's entry criteria.


     If you're still seeing the issue after these steps, feel free to share:
    • The type of record you're working with (e.g., Order, Custom Entity).
    • Whether you're using a background workflow, real-time workflow, or Power Automate.
    • Screenshots or more details about when the error appears.
    Happy to help you troubleshoot further, monkey mart!
  • Suggested answer
    DAnny3211 Profile Picture
    11,397 on at

    Hi,

     

    The error message "The workflow is not in running state; it was completed or cancelled" typically occurs in Dynamics 365 when an attempt is made to interact with a workflow that has already finished its execution or has been manually cancelled.

     

    Here are a few steps to help resolve this issue:

     

    1. Verify Workflow Status:

       

      • Go to the workflow history for the affected record.

      • Confirm whether the workflow is marked as Completed, Cancelled, or Failed.

    2. Check Trigger Conditions:

       

      • Ensure the workflow is configured to trigger under the correct conditions.

      • If it's set to run only once or under specific criteria, it may not restart unless those conditions are met again.

    3. Restart or Recreate Workflow:

       

      • If the workflow needs to be re-executed, you may need to manually restart it or create a new instance.

      • Alternatively, consider designing the workflow to allow re-submission or re-approval.

    4. Review Approval Logic:

       

      • If this is part of an approval process, ensure that the workflow is still active and that the approval steps haven’t been bypassed or invalidated.

    5. Use Power Automate for Flexibility:

       

      • If the built-in workflow engine is too rigid, consider using Power Automate to design a more flexible approval flow that can handle retries and conditional logic.


    6.  
     

    Please verify if this helps guide your troubleshooting.

     

    Thanks and best regards,

    Daniele

    Note: This response was prepared with support from Copilot to ensure clarity and completeness.

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…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Martin Dráb Profile Picture

Martin Dráb 49 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 38 Super User 2025 Season 2

#3
#ManoVerse Profile Picture

#ManoVerse 31

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans