Flexi Tasks Cancelling for No Reason

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?

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.

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.

anyway, I would check whether task form is valid and there are no errors on single controls or in javascript.

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.

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.

since you say it's heavily used list, any chance you hit limit of  max possible permission settings per list?

https://technet.microsoft.com/en-us/library/gg128955.aspx

Hello Marian and Andrew to answer your questions we're at 4k items at the moment with a 15k threshold so we're good on that front.

The Set Permissions action is modifying the list item to only be viewable by the approver SP group and the Operating Company (we have 8 OpCo's and they can't see each other's items) as well as give another SP group Read permissions.

Hi everyone I've figured it out! I use an SP list that my workflow looks at to determine what people and groups get added to the individual item permissions. Turns out one of the users in that list no longer works for the company and that account was deleted. So the workflow would error when trying to add that account to a variable. Good to know for future reference. Thanks everyone for your help!