You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Feature Request: Task Error Handlers for Forms

posted on November 12, 2020

Hello,

We process a massive number of forms, and with such a large number of processes running 24/7 we inevitably run into occasional issues. One of the most common is an HTTP communication error that pops up when LFDS fails to respond to an authentication attempt.

For Forms and Workflow we are using LFDS accounts, so when LFDS fails to respond it causes Forms processes to be suspended. In Workflow, we can configure these errors to retry automatically after a certain amount of time, but we don't seem to have the same option in Forms.

Although Forms will automatically retry on certain errors, it seems that when this happens the only way to get things moving again is to go into the application and manually retry. In my experience, the retry has always been successful since this is really just a sporadic issue.

We're still trying to track down the root cause of these communication errors, and the new notification options are helpful in detecting them, but what I'd love to see is similar configuration options to what we have in Workflow so we can tell Forms which types of errors should trigger an automatic retry, which should not, and which should cause the instance to terminate.

1 0
replied on November 12, 2020

What types of tasks did Forms suspended at? Forms has auto retry functionalities for service tasks(workflow service task, save to repository service task, email service task). By default the auto retry for workflow service task is disabled per the feeback from https://answers.laserfiche.com/questions/124899/Form-kicked-off-300-workflow-instances-in-12-minutes, but you can enable it by changing AutoRetryExcludeWorkFlow option in cf_options table to true and restart the Laserfiche Forms Routing Service to make it take effect. It is a system level option.

0 0
replied on November 13, 2020 Show version history

Thank you for the information. If that's the case, then it sounds like something is not behaving properly in our environment.

The issue occurred again yesterday at 4PM on a Save to Repository task and it has not automatically retried.

I've seen many like this one stuck for days until we initiate a manual retry.

 

0 0
replied on November 16, 2020

Auto retry functionality is added in Forms 10.2.0. Can you check from the cf_options table what is the value for optionname with "AutoRetry"? It should be "true" by default if you never changed it before. If it is "false", you can change it to "false" and restart Laserfiche Forms Routing Service to make it take effect.

0 0
replied on November 16, 2020

We're currently on 10.4.1.164 and I confirmed that AutoRetry is set to true in the db.

I do want to note that many tasks do auto-retry, it just doesn't seem to happen with this particular error.

0 0
replied on November 22, 2020

The auto retry for save to repository service task currently only work when get LFF3005-UnableToConnectToLFServer error, it will not auto retry when get other errors, we are revisiting this behavior to see how to improve it.

1 0
replied on November 23, 2020

Thanks Xiuhong,

That explains why it doesn't retry on this specific error. Back to my original post, it would be great if we had an option for advanced error handling configuration like we do in Workflow so we can set our own rules.

0 0
replied on April 15, 2022

This bug has been fixed in Forms 11. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.