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

Question

Question

Failed to invoke workflow 'WFName', the maximum invoke depth has been reached (32) [0700-WF10]

asked on November 9, 2017 Show version history

I am processing documents and invoking workflows to move through the process and when I get to the end, I invoke the starting process to move to the next batch.  After a few hours of running, my process stops because the maximum invoke depth has been reached.  I see in Workflow Error 0700-WF10 with "Invoke Workflow" Activity that the limit is 32 to prevent runaway workflows but if this is not a runaway workflow, how can I work around it?

My process is this:

Workflow A - Looks for Documents in processing folder.  Invokes Workflow B on any found documents.  Waits for process folder to empty.  Invokes Workflow C and then ends.

 

Workflow B - Process document and move it into archive structure.

 

Workflow C - Assembles batch of documents in processing folder and then invokes Workflow A.  If it finds no documents to assemble in the processing folder, it ends without invoking anything else.

0 0

Answer

SELECTED ANSWER
replied on November 9, 2017

That setup can generate an infinite loop though. Why not run A on a schedule instead (maybe set to one instance at a time only)?

Tech Support can give you instructions on how to raise the maximum invoke depth, but it is a server-wide limit, so increasing it makes stopping infinite loops harder. I won't post the instructions here because it's one of those settings that should only be changed with a clear understanding of the implications on performance.

0 0
replied on November 10, 2017

Thank you for the reply.  I have developed a workaround that is working fairly well.

0 0
replied on February 10, 2023

@████████

Would you mind sharing the workaround you created for this?

0 0

Replies

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

Sign in to reply to this post.