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

Question

Question

Shouldn't retrieve field values be a read action, not a change action?

asked on March 1, 2022

I have been trying to figure this out for years and it is what caused me to create my first and last infinite loop in workflow. Since then everyone I see who creates an infinite loop does it for the same reason, they don't believe they are creating an infinite loop.

Is it logical that the activity retrieve field values is a change operation, rather than a read operation.

Situation.

Customer creates a workflow that retrieves field values from the starting entry.

Customer creates a starting rule for on entry changed and does not exclude the workflow service account.

We train them not to do this, but have no logical explanation of how it is an infinite loop. For it to be an infinite loop, workflow would have to change the metadata.

0 0

Replies

replied on March 2, 2022

Retrieve Field Values does not modify the document. What does the first workflow do with the data it reads from the document?

1 0
replied on March 2, 2022

It puts it in a token, I can prove it modifies the document using the subscriber trace logs.

Will try to get some screenshots.

0 0
replied on March 2, 2022

Audit Trail would be the way to confirm it. Subscriber Trace logs don't show you which workflow generated the change. You might be able to use the Subscriber Trace by giving your workflow a different connection profile with a user not used anywhere else.

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

Sign in to reply to this post.