SharePoint 2010 custom workflow developed using Visual Studio RRS feed

  • Question

  • Hello Folks,

    We have developed custom SharePoint 2010 sequential workflow using Visual Studio for SharePoint 2013 and deployed to Dev, Testing and Production. We had to develop SharePoint 2010 workflow for SharePoint 2013 because of complex functionality to be implemented as per business requirement. The workflow code runs well & good if it is running until certain extent of SharePoint library items (the number of workflows instantiated are varying based on system performance) in the SharePoint document library and it exceeds more than 20 or 30 then it is failing on running on those items. We see the below errors.

    1. Cobalt error was thrown..

    2. Save Conflict Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes....

    Current workaround solution provided: We increased the workflow throttle, batch size. It handled the above errors to certain extent such as, as long as the system resources (90% cpu, 3.8 GB memory utilization)  availability but later it stuck up and stropped workflow running hence we see the workflow status as "Failed on start (retrying..), Error Occurred".

    For your knowledge: The code which we wrote will handle to go through the documents from drop off library and do below before moving to respective sites/libraries/folders/.

    1. Rename the document name as per configured values

    2. Get / create the list of sites / libraries list / folders to which the document needs to be moved

    3. Flush / move the documents to respective destination places.

    4. Apply Item level permissions on the item after moved to destination library

    Appreciated your help about workaround solution for the same.



    Friday, May 1, 2015 3:55 PM


  • Hi Janaiah,

    According to your description, it seems more like an issue of the limited system resource.

    As a suggestion, instead of using workflow in this scenario, if creating a timer job and handling the operations there periodically, it should help to split the burden of your server into different periods.

    More information about custom timer job:


    Feel free to reply if there any findings or any better approach on this issue.


    Patrick Liang

    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Proposed as answer by Dennis Guo Thursday, May 14, 2015 9:25 AM
    • Marked as answer by Dennis Guo Monday, May 18, 2015 1:14 AM
    Tuesday, May 5, 2015 3:03 AM