Question

form stuck in a terminated workflow

Forms

Updated February 18, 2022

asked on October 5, 2016 • Show version history

I have a form setup in the forms portal. I am extracting the information from that form and putting it in external tables. In the beginning I did not have all the fields set to the correct size, so I have 3 forms stuck in the workflow. I need to be able to move the form from its current step "Election Records Created" to the "Waiting for Updates" step so I can send the form back through to get the data. How can this be done?

0 0

Replies

replied on October 6, 2016

If you go to Instance Monitoring, you should be able to see those instances in the list of processes with suspended tasks. You can have them retry the task (which will start a new Workflow instance).

0 0

replied on October 19, 2016

No, that does not work. They are stuck in the middle of the workflow and the retry just aborts. I need to move them by changing the SQL data.

0 0

replied on November 1, 2016

Hi All,

I'm having a similar issue here running 10.1, it seems that Forms doesn't realise when a Workflow task has been terminated. In Forms it shows the current step as being the Workflow task, and when looking in the Workflow Designer the WF for that instance was terminated due to an error. Forms does not show this instance as being "Suspended" however - it is simply sitting in Forms and we are unable to "Retry" the task because Forms doesn't seem to think there are any problems with it.

Has anyone else seen this or is there a way to manually retry a Workflow task?

Thanks, Dan

0 0

replied on November 1, 2016

See this feature request: http://answers.laserfiche.com/questions/108085/Feature-Request-Ability-to-Detect-if-Workflow-Terminated-and-Route

0 0

replied on November 1, 2016

Thanks Blake, this would be useful but in my case it's not even suspending the instance so that I can retry it, it simply just stops and you can't do anything with it at all

0 0

replied on November 1, 2016

Correct, but the feature request would take care of that issue as well because the idea is that Workflow would communicate back terminations to Forms and then allow Forms to do something in response.

0 0

replied on October 9, 2019 • Show version history

The Feature Request for Forms to be able to detect terminated Workflows would be very useful.

Currently, your best option would be to update the Forms process by changing the Workflow Service Task to "No" where it specifies to "Wait for the Workflow to complete before continuing"; that may update the process for those 3 Forms in route, and allow them to move past that service task even though the Workflows are not complete.

If not, the only other option you have is to terminate those 3 processes, then open the Forms to view the variables (or Form values), and start 3 new processes with all of the same information.

I'm assuming since the original Forms processes have failed to complete and the Workflows terminated, that none of the data has successfully been added to the external tables; so, starting a new process shouldn't result in any duplicate data. If some of the data IS already in the external tables (but not all), then you may need to remove the data that did get added by those 3 processes before starting the new instances.

0 0

replied on February 18, 2022

Since Forms 10.4.2, you can skip or retry the in progress workflow service task to make the process continue.

0 0

You are not allowed to follow up in this post.

Question

Question

form stuck in a terminated workflow

Replies

Sign in to reply to this post.