Hi Ken, I told you:

The forms have the rule that if a workflow does not start within 30 seconds, present the error that we reported

Our error was the following:
In the workflows that gave an error, we had the activity "Retrieve Business Process Variables" that obtained approximately 200 variables of forms, which caused the work flow to take about 40 seconds to start and to present the error "The call The Laserfiche Workflow API was unsuccessful. (The operation has expired.) [LFF5203-WFServerApiFault] ".

The solution was to choose fewer variables in the activity "Retrieve Business Process Variables" so that the workflow takes less than 30 seconds to start.

Hi Harold,

I don't recall us ever communicating on this issue but thanks for the response.

Looking through the various logs I do see Forms giving up after 30 seconds if the workflow does not start but I'm not quite sure how the number of variables being retrieved has to do with delay of the workflow starting. Once the workflow starts, the activity log in the workflow indicates it takes on average 1 second to retrieve the BP variables. Plus, this problem only occurs occasionally. I would think it would happen more often if this was truly the cause.

At least I have a better understand of the problem and can continue to research.

Thanks again

Good Afternoon,

Would someone from Laserfiche be able to tell us if we can manually change the amount of time Forms waits for the workflow process to start?

This response was the one that I received from Laserfiche support:

On the Workflow Server machine, go to the registry to HKEY_LOCAL_MACHINE \ SOFTWARE \ Laserfiche \ Workflow \ Options and create a new dword called "OperationTimeout" and set the value to be 300 (decimal). Create the "Options" key if it does not already exist.

After making this change, please perform an IIS reset and also restart the Workflow Server service.

Now try Forms again.

Thanks!