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

Question

Question

workflow 8.3.1 Entry Not Found [0472-WF1]

asked on November 19, 2014

I have two workflows that do the exact same thing.  WF 1 utilizies a wait condition before moving documents.  WF 2 runs on a schedule with minor changes to the workflow to search repository to find documents that meet the criteria then move them.  I get the error on WF 2
and can not figure out why!  Any help would be appreciated.

Thanks

 

John

 

0 0

Answer

APPROVED ANSWER
replied on November 19, 2014

In your second workflow, you indicate that it's based on a schedule. However, it appears that all the routing activities are still set to route the starting entry which wouldn't exist. With the scheduled workflow, the idea would be that you first search for the entries that you want to process (which it looks like you do) and then you'll need to loop through each result and then route that entry accordingly.

1 0
replied on November 20, 2014

Thanks I will look into that and post result

0 0
replied on January 23, 2020

Here it is almost 6 years later, and this post was very helpful to me. 

I had a scheduled Workflow that would run successfully if I started it manually, but if relying on the Scheduler, the Workflow would stop when it had to route the document to a folder (which was the whole point of the Workflow).  When looking at messages for the halted Workflow I saw the following:

Entry not found. [0472-WF1]

Based on the information from Alexander Huang above, I did the following:

Changed the "Route Entry to Folder" to "For Each Entry" and "Current Entry".

That did the trick.  

The Workflow is now looking for and moving documents as expected, on schedule.

Thanks to all who posted here.

It was a big help.

Christine

0 0

Replies

replied on November 19, 2014

In WF 2 here is where I get the error:

Route Entry to Found 2:
Move the Starting Entry to %(SearchRepositoryForExistingFolderinsideActive_FirstResult_FullPath)\%(RetrieveFieldValues_Document Category)
 

0 0
replied on November 19, 2014

Sounds like a permissions issue. Does the Laserfiche User workflow is running as have permissions to this location?

0 0
replied on November 19, 2014

I dont think it is permissions I basically copied WF 1 and made some modifications.  It locates the folder but can not find the entry to move into the folder.  It works fine with the wait condition but bombs out with the schedule.

WF 2.jpg
WF 2.jpg (121.18 KB)
0 0
replied on November 19, 2014 Show version history

I see now, the picture makes it much more clear.

Basically, when you start a scheduled task, you do not have a starting entry unless you set one specifically. This is why your workflow is erroring when you get to that part of the Workflow.

Do you plan to keep both versions of the Workflow running? If so I would recommend having your scheduled task do the search, go in to your For Each Entry loop,  and then invoke Workflow #1 if it makes sense to. This way you do not have to maintain two separate versions of the workflow that essentially do the same thing.

If they should remain separate you will most likely want to move the entire Decision tree with the Query Data task into your For Each Entry loop as I think you want to go through all that logic/tasks for every entry that returns back in the search results instead of just once. You will also want to target the output of the current Entry for all the tasks below it such as move and metadata changes.

 

Hopefully that makes sense.

 

 

0 0
replied on December 1, 2014

The issue has been resolved by moving the rest of the workflow  into the For this entry activity.

Thanks for all the help

 

0 0
replied on October 27, 2015

I have a similar problem.  The workflow creates a folder if one does not exist; that works. However, in both cases where the folder exists or the workflow creates the folder, the documents are moved to a \False folder in the main repository branch; this \False folder is created by the workflow by default.  I am using %(SearchRepository7_FirstResult_Path) in the Destination field of the Route Entry activity, and  %(CreateFolder_Created Parent Folder) in the Destination field of the Move Entry activity.

ExampleWkflw.docx (265.51 KB)
0 0
replied on October 27, 2015

There's not enough to make a good guess. Have you looked at the instance details to see why the condition was not satisfied in the first branch?

0 0
replied on October 27, 2015

Yes, I believe so; attached.

0 0
replied on October 27, 2015

I was asking about the conditions tab in instance details. But based on the tokens tab, are you checking is the Routing decision checking if the search returned any results? If it did, it moves the entry into the same folder as the first hit of this second search and if it didn't, then it creates a folder and moves the entry in it?

If that's the case, you want to use %(CreateEntry_OutputEntry_FullPath) as the destination. %(CreateFolder_Created Parent Folder) is just a true/false flag that indicates whether the folder existed or the activity created it, not the actual path.

0 0
replied on October 28, 2015

Sorry; the conditions image is attached w/messages.  Yes, the system finds the file, create the folder accurately, but does not move the file into the created folder.  It creates and moves the file into a FALSE folder.

I tried using %(CreateEntry_OutputEntry_FullPath) but that does not appear to work.

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

Sign in to reply to this post.