Question

How to fix instances suspended at a Save to Repository step?

Forms

Updated February 12, 2024

asked on January 7, 2016 • Show version history

Thanks to Forms 10 and the Instance Monitoring we can now see how many suspended tasks there are throughout all of our processes. I have since found out that we have 8 instances that are suspended at Save to Repository steps in their corresponding processes. When I tell it to retry them, it is not successful. How do I get these instances to successfully go or find out why they don't successfully save to the repository?

3 0

Answer

SELECTED ANSWER

replied on January 8, 2016

Hi Blake,

Forms don't allow modify submitted data on the fly. So you can temporarily loose the Metadata template field validation and then retry the STR task, and flip the template field restriction back.

2 0

Replies

replied on January 8, 2016 • Show version history

Hi there,

You can checkout the instance level Error Log to get the error detail when STR failed.

One possible reason could be you can Workflow monitor the same folder and rename the file, which will cause conflict with Forms STR task (when it saves multiple files). If that's the case, you can add delay in the Workflow to ensure it modifies the file after files created by Forms STR complete.

2 0

replied on January 8, 2016

I checked the Instance Error Log and it displays the following message for one of the errors:

An unexpected error has occurred. [LFF502-UnexpectedError]

Details:
URL: 
Error: UnexpectedError
Date: 1/7/2016 11:49:47 AM (Mountain Standard Time)
HTTP Status Code: 500
Instance ID: 13072
Business Process Name: DO: Transcript or Immigration Request
Business Process ID: 11

Other:
Bad field value ('Transcript Status'): Another operation on which this operation depends failed. [9054]
Bad field value ('Date'): Another operation on which this operation depends failed. [9054]
Bad field value ('First Name'): Another operation on which this operation depends failed. [9054]
Bad field value ('Last Name'): Another operation on which this operation depends failed. [9054]
Bad field value ('Alternate Name'): Another operation on which this operation depends failed. [9054]
Bad field value ('School'): Another operation on which this operation depends failed. [9054]
Bad field value ('Graduated'): Another operation on which this operation depends failed. [9054]
Bad field value ('Date of Birth'): Another operation on which this operation depends failed. [9054]
Bad field value ('Phone Number'): Constraint violation on the field "Phone Number" (Phone number must be of the form ###-###-####.
For example, 123-456-7890). [9903]
Bad field value ('Email Address'): Another operation on which this operation depends failed. [9054]
Bad field value ('Payment Type'): Another operation on which this operation depends failed. [9054]
Bad field value ('Amount Paid'): Another operation on which this operation depends failed. [9054]
Bad field value ('Payment Date'): Another operation on which this operation depends failed. [9054]
Bad field value ('Check Number'): Another operation on which this operation depends failed. [9054]
Bad field value ('Media'): Another operation on which this operation depends failed. [9054]
Bad field value ('Notes'): Another operation on which this operation depends failed. [9054]
Bad field value ('Code'): Another operation on which this operation depends failed. [9054]

Stack Trace:
Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException
Message: An unexpected error has occurred. [LFF502-UnexpectedError]
   at Laserfiche.Forms.Routing.SaveToLaserficheService.Execute(Int32 instanceId, IRoutingContext routingContext, RoutingInstanceStatus OriginalStatus)
   at Laserfiche.Forms.Routing.ServiceTask.Execute(Int32 instanceId, IRoutingContext routingContext)

Inner exception: Laserfiche.RepositoryAccess.MultiStatusException
Message: Multistatus response. [9039]
Constraint violation on the field "Phone Number" (Phone number must be of the form ###-###-####.
For example, 123-456-7890). [9903]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Constraint violation on the field "Phone Number" (Phone number must be of the form ###-###-####.
For example, 123-456-7890). [9903]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
   at Laserfiche.RepositoryAccess.EntryInfo.Save()
   at Laserfiche.Forms.CommonUtils.LFHelper.SetValueToTemplateField(EntryInfo lfDoc, String template, FieldValueCollection fvs)

I'm guessing in this case it is failing because of the phone number have a problem with it's formatting. How can I edit the value so it's valid?

2 0

replied on July 7, 2017 • Show version history

Thanks, Abby:

I just had this happen and after looking at your comment about Metadata (on the Template designed for this form once brought into the LF repository), I was able to go into my new fields for this new form and review the sizes for each field. I found one that the applicants were typing in more than 40 characters for a Program Name and the field for the program was set to only 40. Once I changed the field size to allow up to 80 characters, both of the suspended applications came in successfully!

1 0

replied on February 12, 2024

Thanks Abby and Connie,
Once I increased the character limit (in the Template in the Admin Console) for the requestor location field (the error log indicated was too long), I was able to successfully retry the suspended forms.

Appreciate your posts!

Christine

0 0

replied on February 12, 2024

Christine, we have a new option now, too. I'm not sure if it was the Upgrade to Version 10 or 11, but I can now edit the variables to make them smaller rather than changing how many characters are allowed in fields. So, one example I can think of is a Vendor Name... if someone typed in a vendor name that was too long, I could go in and change what they entered, rather than make the field larger.

I have seen where people have submitted something in a field that is totally inappropriate for the field and I was forced to temporarily increase the field limit, get the form to finish, then go back and change back the field to what it should be AND change the newly saved entry so the template field shows something more appropriate. Better to just correct what the user wrongly filled in.

2 0

You are not allowed to follow up in this post.

Question

Question

How to fix instances suspended at a Save to Repository step?

Answer

Replies

Sign in to reply to this post.