Question

Another operation on which this operation depends failed [9054]

Workflow

Updated July 22, 2022

asked on October 17, 2019 • Show version history

I have a workflow (10.0) that runs daily, iterating through more than 1000 documents, but about 50% of the time it throws a warning on the same action. There's a "Route Entry to Folder" action that also assigns a field, and for ONE document (it was two yesterday, but usually one) it throws a warning.

Route Entry to Terminated Folder
(SetTemplate) The data assigned to field 'Contract Status' is not valid. 9039 [Multistatus response. [9039]
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 t

I would think that this is due to an invalid value being assigned to a field, but the action only assigns to one field, and the value assigned is selected from a drop-down. It's also the exactly same value for every document in the loop that hits that action, but only has the issue for one document most of the time.

EDIT: I've found the solution

We made some changes to the fields in the repository such as making some fields required that were not required before. This did not affect documents that were already in the repository with those fields not filled in, but trying to edit and save the metadata after that would prevent your changes until those required fields have values. If you try to do it in the client, it directly tells you which field to fill in. However, the workflow only throws the warning I mentioned above, which is not helpful because the message is cut off before it gets to which field has an issue.

2 0

Replies

replied on July 12, 2022

How is it done in the case when there are "object table" in the form? , what configuration should the metadata have????

Thank you for your support.

1 0

replied on July 12, 2022

Hi Gustavo,

I don't understand your question. Is this related to the issue I had, or do you need to open a new question with more information and possibly a screenshot?

1 0

replied on July 12, 2022

Hello Brian,
I have a similar problem, I am trying to save the information of a Form in a repository (it has textbox and multiple Tables),
For which I have created a metadata template, each field configured with each data type.
But when selecting "Send" the Process Automation comes out in "Suspended State", reviewing the error log, I found that I have problems
with the fields (attached the image), which may be happening.
I am assuming that I have misconfigured the data type of the Metadata template, in the case for tables.

First of all, I thank you for your support.

Error_GenerateMetadata_Table_forms.jpg (424.68 KB)

| Download

1 0

replied on July 22, 2022

Hi @████████, apologies for the delayed response. I completely forgot to get back to you.

From looking at your message:

The parameter is out of range or too long. [9020]
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]
The parameter is out of range or too long. [9020]
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...

The message is cut off, so I cannot see if there are any other problematic fields, but the lines that have the 9020 error indicate which field actually had the issue, there the ones with the 9054 error indicate fields that are fine. From counting the lines in your error, I can see that field 1 and 9 have the error "The parameter is out of range or too long. [9020]"

This error means that the value from the form is either longer than the size of the field, or that the field type is incompatible with the value, or that the field has a constraint that the value is violating. I'm not sure which fields are 1st and 9th in your Save to Repository action, but you will need to check those fields and the values attempting to be saved and make sure the field is large enough to fit the value and is a compatible type. For example, if you have a Number field, and the value being saved is "ABC," it will not be able to save the field because ABC is not a number.

I hope that helps you if you are still having trouble with this.

0 0

replied on October 18, 2019

You will need to capture the value of the token to debug, it should be static, but the system is saying it is invalid. This mean it needs to be looked at in the moment it fails to see why this "static" value is not what you expect it to be.

Put the Assign Field Values object into a Try Catch, in the Catch put a Token Tracker to record the value in the logs.

Or just run the workflow on the problem entry, with a token tracker in the workflow to see why the value is bad.

0 0

replied on October 21, 2019

1. Unfortunately you can't use a try-catch block with an activity that only throws a warning, not an error.

2. What value would I track in the Token Tracker if it's a static value?

0 0

replied on October 21, 2019

Figured it out. Editing my original post.

0 0

replied on October 18, 2019

Where do the repeated 9054 errors come from?

0 0

replied on October 21, 2019

Can you be more specific with this question?

0 0

replied on October 21, 2019

Figured it out. Editing my original post.

0 0

replied on December 13, 2021

I had a similar issue, but the cause of my problem was the length of the field. The workflow template was set to 50 characters, while the form was submitting 100+.

I updated and set the limit of both fields to 160. Haven't had a problem since.

0 0

You are not allowed to follow up in this post.

Question

Question

Another operation on which this operation depends failed [9054]

Replies

Sign in to reply to this post.