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

Question

Question

For Each Row is not getting executed in Workflow

asked on April 10, 2016

Dear Support,

 

We have an workflow with QueryDB and assigning values in the token.

In some instances the Workflow does not go in to the For each loop though QueryDB fetch rows. But do not see any messages or any error logs.

Find the below screenshot of the Workflow executed, where it did not execute only For each Row though it found rows. 

This issue is intermittent, and not able to figure out issue without any logs or errors. How can we resolve this issue?

Regards,

Kirubaa

2 0

Replies

replied on April 10, 2016

The first thing I would do is put in a "Track Tokens" just before the routing condition that is set to record all rows and any data used in your conditions. 

 

I'm not sure how your query is setup, but if you capture the data you may be able to spot something that helps make sense of the issue. And at worst case you'll have data to report up to laserfiche to help troubleshoot the issue. 

0 0
replied on April 10, 2016

Thank you for your reply Chris!

I'm fetching the 1st row of the query result only. So either it need to be either success or failure in the query. The branch having issue on the success of the row returned condition.

 

Track token would help, but in production system we do not experiment this way.

 

 

0 0
replied on April 11, 2016 Show version history

Track tokens doesn't actually change anything with your workflow though (aside from saving a new version with it added). All track tokens does is store the tokens in the workflow database. This does cause a little bit more traffic in the database but you can limit it to just that specific token only.  this way when you go into workflow designer and look at the history (like what you are seeing here) you will have a token tab that includes the tokens you decided to track. 

 

Think of it as turning on logging. I wouldn't consider this an experiment whatsoever, it's a troubleshooting tool in the same way logging is. 

0 0
replied on January 3, 2017

I have this issue as well.  I have a custom query with a for each row activity after it, which intermittently does not run even when rows are returned by the query.

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

Sign in to reply to this post.