Forms Triggering Workflow - Error: (413) Request Entity Too Large

asked on December 20, 2023

I have a very complex forms process that includes multiple workflows and other activities.

It's been running for several months with a dozen or so instances each month, and I haven't encountered this error before.

After each user task, the system runs a couple workflows and then starts the next task. Much of the tasks are repeats of the same task as the user makes changes and then it returns to them for additional work/notes/comments. So this particular instance has an extensive history of tasks and workflows.

After the last user task completed, and it attempted to start the workflows, the instance was suspended with errors calling Workflow. Attempts to "Retry" result in the same error.

I'm listing the details of the error from the Event View logs below - but I'm wondering if anyone has encountered this error before and has any advice on how to work around it?

Thank you.

Event Viewer:

An unexpected error has occurred. [LFF502-UnexpectedError]

Details:
URL: 
Error: UnexpectedError
Date: 12/20/2023 4:05:03 PM (Mountain Standard Time)
HTTP Status Code: 500
Business Process ID: 294
Instance ID: 311080
Business Process Name: Loan Presentation - Approval/Annual Review

Stack Trace:
Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException
Message: An unexpected error has occurred. [LFF502-UnexpectedError]


Inner exception: System.Net.WebException
Message: The remote server returned an error: (413) Request Entity Too Large.
   at System.Net.HttpWebRequest.GetResponse()
   at Laserfiche.Forms.Routing.WrapHttpWebRequest.GetResponse()
   at Laserfiche.Forms.Routing.LFWorkflowService.Execute(Int32 instanceId, IRoutingContext routingContext, RoutingInstanceStatus OriginalStatus)
   at Laserfiche.Forms.Routing.ServiceTask.Execute(Int32 instanceId, IRoutingContext routingContext)

0 0

replied on December 20, 2023

Thank you so much @████████ !

I had seen that other post, but didn't realize that it would apply to Forms calling Workflow in addition to the API stuff the other post was talking about, so I hadn't tried the solution.

But now, I applied the solution/change to the Web.Config file, restarted the Workflow service, and retried the suspended instance, and this time it worked as expected without the errors.

replied on March 27

@████████

I used your fix for this exact problem after upgrading to Forms 12. Thank you!

1 0

Question

Question

Forms Triggering Workflow - Error: (413) Request Entity Too Large

Answer

Replies

Sign in to reply to this post.