I see a thread related here: Sharepoint Workflow - Conditional auto approval

One challenge I have that's different is that we are dealing with date context specific scenario. Here's what we want to do- Auto approve tasks when they are past due.

My initial though was that the default outcome feature of the task process does this but that's not what I'm seeing. Let me know if I missed something here.

Alternatively, I was hoping to add a logic somewhere in sharepoint designer that says if the due date is past today then approve the task automatically but couldn't really make this happen since a task process is a singular chunk of sequential process and I can't really add something "in the middle" of that. Is this doable? Are there alternative methods to achieve this?

Thanks for any guidance. This is for SharePoint 2013

  • 1
    Create another workflow/timerjob that runs daily and approves tasks that are past due date. This approach is straight forward and is easy to implement Nov 21, 2014 at 23:22
  • Thank You, Amal. Will definitely look into this option as we try to get access to a dev box with visual studio. I'm also curious what the purpose of that "default outcome" is in SharePoint Designer. The team is going to need me to justify this route of custom solution.
    – zigzag
    Nov 24, 2014 at 2:56

1 Answer 1


Amal's response really pointed me in the right direction.

Couple lessons that are helpful in implementing his recommendation:

I found that a SP2013 WF can trigger a SP2010 WF but not another SP2013 WF. This means that the second WF on the task list needs to be a SP2010 WF is the task is generated by a SP2013 WF. This is due to the recursion feature: https://blogs.msdn.microsoft.com/sridhara/2014/08/19/fix-sharepoint-2013-workflow-recursion-prevention-part-1/

Though you probably already figured this out I found that %complete field needs to be set to 1 not 100.

Also default outcome is related to the content type. For the SP WF task content type set the outcome to "Approved" (This is what the Approved button does for default content type besides setting the task to complete and %complete to 1)

Lastly I found that a race condition can exist if the task is created and the due date has already expired. The task WF will still fire and auto complete the task, but if the source WF (WF that generated the task) has the condition checked to wait for all responses then it will not pickup that the task has been auto completed. To solve this I added a delay condition to wait for a couple min before executing the task auto approval WF.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.