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

Question

Question

Multiple Instances of Same Workflow Are Mixing Documents

asked on July 15, 2021

I have a workflow that takes a multi-page document generated by Snapshot, uses Pattern Matching (RegEx) to extract a unique identifier for each page, extracts the page, looks up the identifier in a separate SQL database to get more information about the page, then creates a new document, moves that page into the document and uses the SQL data to insert metadata, name the document, and determine the path to put it into our Laserfiche repository. There is a starting rule that watches a folder, then triggers the workflow when a document is created there.

If we create a document in the watch folder, the workflow is triggered; then while that instance of workflow is still running, a second document is created in the watch folder. The result is that pages from the second document will get mixed in with the first document. Where each page from the source should be a single page in the resulting documents, some of the resulting documents have 2 pages (one page from each of the source documents), so we're losing pages from the second document because they're mixed in with the first, and don't have the right metadata attached and are in the wrong folder.

Is this a known bug or is there a setting I missed somewhere?

0 0

Answer

SELECTED ANSWER
replied on July 19, 2021

When you have two instances of your workflow running simultaneously, how do they avoid copying the page into the same document? It sounds like naming the document comes after creating it, so I'm guessing they all create a document using the same placeholder name? That's probably where it goes wrong, that your workflow is grabbing the document created by another instance instead of creating its own.

Do you have anything available to uniquely name the destination document? The entry id of the source document could be useful for that.

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.