Contents
Why did my workflow get stuck on started?
Based on what I read, there are several reasons workflows will get stuck on started. My particular situation might have been one of two (or multiple/all) things: 1. The ciphers on workflow manager did not match the front-end servers 2. SSL and TLS Settings did not marry up.
So as you can see, the Workflow can’t do anything because it can’t set the value since it is not checked out. You don’t get that information in older versions of SharePoint so hence this post. Remove the checkout required from the library.
Which is the first step in the workflow?
The first step in the workflow is to change the workflow status to ‘Pending’ however it doesn’t even get to that stage which tells me the Workflow itself isn’t actually starting to run. I’ve given the user submitting the form full control over the list, however, this has not helped.
Do you need permission to access a list of workflows?
By default, the workflow doesn’t have permissions to access the list where the Workflows generally run at permission level equivalent to write. Also , The user doesn’t have Contribute permission on the list.
How to stop infinite loop when workflow modifies L…?
I have a custom approval (NOT using the approval actions in FLOW) process I built using standard SharePoint and Office 365 Connectors. The FLOW has some delays in it as well. The FLOW triggers on “When a file is created or modified (Properties only). The problem is that the workflow may run for a few days, waiting for a status change.
As far as configuration is concerned I can see the 2013 workflow option in SharePoint designer, upon clicking the workflow service application I can see “Workflow is Connected” message I went through the same issue, here’s how I resolved it:
Why does workflow run after a status change?
The problem is that the workflow may run for a few days, waiting for a status change. If Joe User comes along and makes a change to the file or to any of it’s properties…that kicks off the FLOW again.