I have a workflow that keeps cancelling for no reason at the Flexi Task level. IT does this immediately when the workflow is fired or terminated then refired. Before the flexi task the workflow doesn't do much except set some variables and a couple of fields in the SharePoint list (I have built an Infopath form over the list FYI) it also sets individual Item Permissions on the list item. I have checked and the initiators and approvers in the Flexi task all have contribute rights to the list item. Any ideas. Thanks very much in advance.
Solved! Go to Solution.
do you get any error?
do you get any outcome?
have you tried to configure OTHER branch whether flexi task wouldn't go down that way?
what do you exactly mean with this:
when the workflow is fired or terminated then refired
when you start the workflow and then you start it once again, you get a error?
when you terminate the workflow and then you start it once again, you get the same error as well?
What are the starting conditions for your workflow? Does it start automatically on creation or modification or is it purely started manually?
Are you saying that when it starts, the flexi task gets cancelled?
I can see why the flexi task gets cancelled if you terminate the workflow, that is expected behaviour.
Hello Marian thank you for your reply. I will answer your questions in order
Yes I get Error Occured the exact message is "An error has occurred in Job Open Form Workflow."
No outcome it just errors.
This workflow is fairly linear. It hits a State Machine and Immediately hits the Flexi Task where it just cancels. I will attach a screenshot
I created a very simple workflow that will terminate any running workflows and just restart the main workflow that I'm talking about
Yes to both the last questions
I hope this helps.
Thanks so much for your reply as well Cassy.
It is started upon creation of a list item.
It actually officially says "Not Required" you can see in the screenshot I posted for Marian
I only terminate and refire after the error.
Does any of this sound like something you've seen before?
I haven't seen this error yet.
some hints, thought
- I would definitely put a commit pending changes or pause action right before flexi task.
you perform some item updates and permission changes down the way and they need not be effectively be applied before flexi task is reached (if you eg. grant permissions for task approver). see following link for further insights Designing your Workflow - Commit Pending Changes Action NW2010 & NW2013
- the error message reference some 'Job Open Form Workflow'. 'job open form' sounds a bit uncommon wording.
if you couldn't spot a problem there, try to export the form definition (to have a backup) and then remove. that way default task form is restored.
try to run workflow whether flexi task will correctly in this setup.
- due to uncommon and unclear error message, if you have customized workflow start form, try to check its validity as well.
but that doesn't seems likely to be a reason since several workflow step has been executed.
if above will not help, post configuration of flexi task as well.
Agree about commit pending changes after the Permission changes. Though I wonder what permissions are changing to on what item. Also, is the task able to identify the user it is assigned to? I've seen that post a Not Required. Can you assign it to yourself and create the task?
Also, what user is publishing the workflow?
OK so I tried the Commit Pending Changes and it didn't work even tried a Pause and it didn't work. BUT I disabled the Item Permissions and lo and behold it went through. Now this is a fairly heavily used list and has been so for almost a year. That workflow was working up until about two weeks ago just the way it was. Any ideas on what could have happened? And more importantly what can I do here. I need those permissions.
Hi Andrew as I replied to Marian something's going on with the permissions for sure. To answer your question yes it is able to and no I can't assign it to myself. The odd part is I conducted a test with some of my end users and it worked.
I'm a little unclear do you mean what users are firing the workflow or actually making changes to it and publishing?
since you say it's heavily used list, any chance you hit limit of max possible permission settings per list?