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

Question

Question

workflow not firing on 2 files - all others working fine

asked on June 4, 2019

Hello,

I have 2 files that are not being moved and can not figure out why.  The conditions on the template are correct and the rule criteria is correct.  All other files are firing...

I have moved to test and have been trying different things but nothing moves the files.  Any other place or tech tips you have to troubleshoot this issue?  Really bazaar...

 

Thanks!

Suesmiley

0 0

Answer

SELECTED ANSWER
replied on June 6, 2019

My guess would be that because the wait condition was already satisfied, it didn't detect who made the change and therefore couldn't obtain the user name.

I would set approval back to "No" then move it back out/in, and have a user who is supposed to do the approval set it to yes to satisfy the wait condition.

2 0

Replies

replied on June 4, 2019

What does it show in the Subscriber Tracer when a change is made to the documents?

Open the Workflow Administration Console, select Monitoring > Subscribers, right-click the subscriber name and select Show Subscriber Trace Log.

That will show you exactly how the conditions are being evaluated.

2 0
replied on June 6, 2019

Thanks for responding :)  Trace only goes back to 5/13/2019 :( 

Creation dates on the documents are 11/13/18 and 11/19/18

 

0 0
replied on June 6, 2019

The "active" trace logs only go back so far, but you might still have older logs on the server depending on the retention period on your workflow logs.

The default configuration will roll them over to a new file after a certain amount of time, but they're usually retained much longer.

The log path is

C:\ProgramData\Laserfiche\WF\ServerData\SubscriberLogs\{servername}

1 0
replied on June 6, 2019

The folders after laserfiche are not the same.  We are on an old United version 10.2.  I'll search on Subscriberlogs or logs...

0 0
replied on June 6, 2019

found them

0 0
replied on June 4, 2019

What are the rules to move the document? 

It seems that another rule may be taking priority.  You may want to go to your wf search and see what rules ran.  You can also look at the rule that did move the other documents to see if it originally found the document or if there was an error on the workflow. 

1 0
replied on June 6, 2019

Thanks for responding.  Sorry for delay.  We are trying to get new Rio environment and had some server issues blow up yesterday.  MUCH better now :)

It is definitely working on other docs.  The workflow itself has not been modified for at least the last year and half (since I started). Attached rules.

Much thanks!

I634962 - 1.PNG
I634962 - 1.PNG (212.46 KB)
0 0
replied on June 6, 2019

Based on that screenshot, the Entry Path condition of your rule is not being met.

Are these documents in a different folder from the others?

0 0
replied on June 6, 2019 Show version history

This is what is on the actual workflow in rules:

Starting Event: Entry Moved
Run workflow on the entry that was moved

If all of these conditions are true
        Entry : Type equals Document
        Entry : Path equals \HUMAN RESOURCES\Dir of Employment Services
        Entry : Template Name equals Tuition Reimbursement
        Entry : Field (HR Review) equals Complete

There is only 1.

So does the Tracer only log Errors or False conditions?

I also checked the document and the template is correct and Complete is selected.  Looks like the other docs that are being processed.

0 0
replied on June 6, 2019

The tracer logs all rule evaluations made for each entry event, but for optimal performance it stops evaluating a rule/group as soon as it find that the conditions cannot be met.

1 0
replied on June 6, 2019

Thank you so much!!  I'll start looking for the needle in this haystack LOL

Do you see any issue with me creating another rule (entry changed) and add a number to the file to see if I can generate a more recent error?  

0 0
replied on June 6, 2019

Adding another rule might have an unexpected impact on other documents. What I would do is just move the document out of the folder then move it back in to manually trigger the rule again on the same documents that didn't work before.

0 0
replied on June 6, 2019

Gotchya.

Tried dragging them out and back in and no triggering sad no tracer log on either file.  So weird...

Any other suggestions??  Move manually to the next step?  Or put in a support ticket?  

Starting to know all the folks in support because of the new install of Rio smiley I haven't bugged them today...  laugh

0 0
replied on June 6, 2019

Wait one!!!  There is an error on the workflow designer search results.

Let me see what's happening.  I'll keep you posted.

0 0
replied on June 6, 2019

Any idea why this may have failed (attachment) when it is working on all other docs...  Network hiccup? 

I634962 - 2.PNG
I634962 3.PNG
I634962 - 2.PNG (120.56 KB)
I634962 3.PNG (138.65 KB)
0 0
replied on June 6, 2019

It looks like no value is being provided for the search parameter. In the workflow configuration, is it set to "a user from a token" and if so, what token is being used?

0 0
replied on June 6, 2019 Show version history

Populating from AD

I634962 - 4.PNG
I634962 - 4.PNG (154.56 KB)
0 0
replied on June 6, 2019

Here is the WF Admin Console screenshot

I634962 5.PNG
I634962 5.PNG (132.9 KB)
0 0
replied on June 6, 2019

Click over to the Tokens tab in the instance details and check the value of that token. Since the instance terminated, newer versions of Workflow automatically track all token value at that point.

2 0
replied on June 6, 2019

Now that's an awesome new feature!

0 0
replied on June 6, 2019

Nice!

Blank :(

Can you tell me any reason why it didn't get populated then and now when I brought the files back in...  The directory has not changed and it is working on other docs.

0 0
SELECTED ANSWER
replied on June 6, 2019

My guess would be that because the wait condition was already satisfied, it didn't detect who made the change and therefore couldn't obtain the user name.

I would set approval back to "No" then move it back out/in, and have a user who is supposed to do the approval set it to yes to satisfy the wait condition.

2 0
replied on June 6, 2019

It's that "initially satisfied" part. This document landed in the folder with everything in place to satisfy the wait conditions. So there was no user changing it, it passed right through.

2 0
replied on June 6, 2019

Hmmmm.  OK.  Thank you so much everyone.  My brain is a little numb with everything and only really getting into trenches now.  I REALLY appreciate the quick and thorough responses.  Lots of lessons here smiley  Enjoy the rest of little friday!!!

0 0
replied on June 6, 2019

That worked!!  Thanks again :)

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

Sign in to reply to this post.