none
SPD 2013 Workflow in SPO will not start when item changed RRS feed

  • Question

  • I have a list in SharePoint online that has a spd 2013 workflow running on it. The settings are to start a workflow when an item is created or modified. 

    • When an item is created workflow A starts normal. 
    • When that same item is changed while the workflow A is started/running, a new workflow will not start. 
    • If workflow A finishes and THEN the item is changed, a new workflow B will start. 
    • If Workflow A is in progress, the item is changed, workflow A finishes, no its not like there is a workflow B waiting in the queue to start. You must first complete workflow A before making a change to an item or else a workflow B will not trigger .
    • trying to manually start the workflow b also does not work. workflow a must first be in a completed state before there is any response to any new workflows.

    hope that makes sense

    • List items are not being created / modified by / and workflows not being initiated by system account
    • tried to remove the list associated to workflow, then re-add, no change
    • checked list settings > wf settings > select workflow > verify start options, looks good
    • checked that all have at least contribute permissions on list and site
    • tried to write a new workflow on the same list, same issue
    • tried to write a new workflow on a new list, same site - same issue
    • tried to write a new workflow on a new list, new site - same issue
    • tried to write a new workflow on a new list, new site, new tenant - same issue
    • and yes the little box is checked in spd to auto start workflows on new and changed items.

    Is this a bug? A workflow should start when an item is modified. 

    ideas? 

    Thanks!

    Wednesday, December 11, 2019 9:46 PM

All replies

  • Since, this is SharePoint Online we can't get much info on it, I would say raise a Microsoft Support Ticket from your SharePoint Online Admin center. They should get back to you with in 24 Hours.

    Thanks & Regards,


    sharath aluri

    Wednesday, December 11, 2019 9:53 PM
  • I did and they said they don't support issues of this nature. 
    Wednesday, December 11, 2019 10:17 PM
  • Hi, Hatey,

    According to your description, it is a tenant level issue. What does the MS support team say about this issue? If possible, please share us with your workflow configuration. I will try to do some tests with it. You can post this issue on userVoice for MS to review if the service request cannot help you.

    Best Regards

    Jerry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Thursday, December 12, 2019 8:40 AM
  • Thanks Jerry, 

    This was Microsoft's response:

    "

    You can actually submit this bug directly to our Engineers so they can review and make some adjustments. To do this, please submit it through our UserVoice. 

    Please understand that we cannot do some adjustments on how it works here but surely our engineers will be able to handle it. That is why it best to get in touch with them directly through UserVoice.

    "

    I thought UserVoice was for feature requests only? In any case, I decided to build out in PowerApps and Flow instead as I do not have time to wait for a resolution on this that may never come. 

    Tuesday, December 17, 2019 11:42 PM
  • Hi, HateyKaty,

    Just for confirmation, the workflow A and B are in fact the same workflow. You goal is to trigger the workflow when the item is created. When the workflow is running, you finished creating and edit the item to trigger the same workflow.

    If this is your scenario, that is a by-default behavior. You can run just one instance of a workflow on an item. It cannot be done. You can set one workflow triggered when created and one triggered when item is modified. 

    Of course you can use Flow to finish your requirements.

    Best Regards

    Jerry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Wednesday, December 18, 2019 9:44 AM
  • Hi, Hatey,

    As we have not heard from you for some days, here is a brief summary about this thread. Hope it will help other community members with similar concerns.

    ======================================================================

    Issue Symptom:

    A workflow is set to be triggered when item is created and modified. OP want to trigger the workflow second time through item modification when the first workflow triggered by item creation is still running.

    =====================================================================

    Possible Cause:

    That is a by-default behavior. You can run just one instance of a workflow on an item. 

    ====================================================================

    Troubleshooting Steps so far:

    Test the workflow in different lists and sites.

    ===================================================================

    Next Step:

    Create two workflows with different triggers.

    =================================================================

    Best Regards

    Jerry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Friday, January 10, 2020 9:32 AM