Hi,
What would cause a Forms Task that initiates a workflow to start the workflow twice instead of once?
Mark
It's hard to say without seeing your process diagram.
Dear Xavier,
My question was a bit general because I had not looked at the process. My intention was to get advise on what to look for when I visit the client. Otherwise I have looked at the process and the issue is that the process posts the error below
The call to Laserfiche Workflow API was not successful. (The operation has timed out.). [LFF5203-WFServerApiFault]
The process does not suspend as usual but goes ahead and triggers the workflow twice. So we have two instances with the same FormsSubmissionID.
Regards,
Mark
You should try changing the timeout settings, so that the activity has more time to run before a timeout is triggered. You can also change the settings, so that timed out workflows aren't re triggered.
how would you do this (change timeouts or stop the autoretry. We are experiencing the same issue after we updated to 10.2 with a form that did not have issues on 10. the form submits the workflow twice and duplicate documents get created.
@████████ where are the timeout settings that you mention in your reply?
i have the same problem.
I have the same issue. Forms invokes WF and should end but causes the instance to repeat.
Hi, is there any status update on this thread? I'm having the same issue with Forms 10.2.1.290
Peter, I found that the "Invoke Business Process" activity in Workflow was causing the forms instance to repeat and start over. Not sure if this is the same case as yours.
hmm. that's interesting David. Thanks for the input. I had a Laserfiche support ticket opened and the recommended solution was to upgrade to 10.3.1 update 1 as they say that this issue was a known bug. See below.
"I believe this is a known issue with Forms 10.2.1.290 and has been patched in 10.3.1 update 1. https://support.laserfiche.com/kb/1013963/list-of-changes-for-laserfiche-forms-10-3-1-update-1
Specifically, bugs 83609 and 82680. What is happening is the Workflow Task in Forms is set to wait for the Workflow to complete, if it takes too long the Forms instance will timeout and suspend the task. The error you are seeing in Forms is observed during this.
Simply upgrading to 10.3.1 update 1 may address the issue, bug 82680. If not, they can add WFResponseTimeout and set the value to prevent the timeout, bug 83609."
Thanks Peter, that's exactly what was happening to me. let me know the results, I will upgrade Forms to 10.3.1 also.