Question

Warning 9014 and 9059

Workflow Version 10

Updated November 8, 2016

asked on November 8, 2016

I have a workflow that does the following:

For each page of the document it creates an empty document, copies the metadata from the starting entry to the new document, moves the first page from the starting entry to the new document, and then invokes a workflow.

It works correctly for the first page of the starting document, but when it gets to the second page it creates the empty document and copies the metadata, but then goes into a waiting status when it gets to the Move Pages activity. In the instance details it gives the following messages: "Entry Locked [9014]" and "Operation failed due to entry sharing violation [9059]".

I read that on a 9059 it will retry, but I have yet to see it do that. I curious though why it thinks the document is locked? The Admin Console does not show any locks when I look. Any ideas?

Workflow Designer 10.0.0.249

1 0

Answer

SELECTED ANSWER

replied on November 8, 2016

I figured it out. I did not configure the Invoke activity correctly. It was set to invoke with the current workflows starting entry, rather than the entry that was created in the repeat.

1 0

Replies

replied on November 8, 2016

Are you sure you don't have any other workflows that start when that entry is created? It's possible that the lock is short lived, so by the time you check for it in LFAdmin, it's gone (but it was long enough to trigger the Workflow retry mechanism).

The default wait time for 9014 and 9059 is 5 minutes, then Workflow will retry the action. You can double-check that in the Workflow Admin Console under Task Error Handlers.

3 0

You are not allowed to follow up in this post.

Question

Question

Warning 9014 and 9059

Answer

Replies

Sign in to reply to this post.