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

Question

Question

Workflow to Kick Off Very Large Form Shows Terminated (Timed Out) Despite Success

asked on January 4, 2018

I have a workflow that is kicking off a very large process in LFForms.  It is working successfully, but I'm getting reports from Workflow indicating that it always terminates with an error that it timed out.

Are there any options or settings to increase how long Workflow waits to get completion confirmation back from Forms before it declares that it timed out?

0 0

Replies

replied on January 4, 2018

Default is 300 seconds. Open Workflow Administration Console, go to server options and double click Advanced Server options to open a hidden application. In this app, go to the tasks tab, the timeout is second to last field.

0 0
replied on January 4, 2018

That's the timeout for deleting completed tasks, not how long a task can last.

0 0
replied on January 4, 2018

What does it mean to delete a completed task? From the history? after only 300 seconds?

0 0
replied on January 4, 2018

@████████ - is there a timeout option that addresses how long a task can last?

0 0
replied on January 4, 2018

There's nothing expose to the user to increase the timeout. You could add a try-catch around it and ignore the message.

0 0
replied on January 4, 2018

I did a try-catch and that just resulted in the form being kicked off multiple times because it is succeeding to kick-off the form, it just thinks it is an error out for taking too long.

0 0
replied on January 4, 2018

I could turn off the termination notices for this workflow, but then I worry about some other issue occurring and not being caught :-(

0 0
replied on January 4, 2018

How did you set up the try-catch? Workflow doesn't resubmit the form on its own.

0 0
replied on January 5, 2018

Sorry, I had set it up to try to start the form and if it got an error to try again, and I'd looped that a couple times.  That was because I hadn't realized that the form was working, just that I was trying to get around the error.

0 0
replied on January 5, 2018

I think I'll do a single try-catch without anything in the catch side of things.  And I definitely won't loop it through again.

Since I know it is working regardless of the timeout error, that will (probably) at least keep it from being flagged as terminated due to the error.

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

Sign in to reply to this post.