Hi,
We have Scheduled Process flow(s), when Flow is triggert there are about around 1000 records.
We see that not all records are processed. If we trigger te flow again then it will not process all records.
Even if i schedule every 5 or 10 min. not all records al processed. Sometimes 0 records are processd even if there are records found.
Is this a default behavior? Or is there an setting to set.
Thanks,
Robin
Best answer by robinsch
Hi,
It seems the issue was that I had multiple conditions without any actions when the condition was true.
The condition I used was a query that checked if the order was in the ap_lock table. If it was, the process would do nothing.
I have removed this condition and added it to the Data Query instead, and now all rows are processing correctly.
As I’m writing this, I’m thinking that maybe I could change the condition to: if the order ID is not in the ap_lock table, then perform the action; otherwise, end the process flow.
But everything is working fine for now.
Robin
It depends on the filter criteria defined in the process flow conditions. The query might be pulling many records, but the updates may be only executing on a subset of that data. Check the query results against the criteria that is defined in the process flow conditions to see if it helps shed some light on this.
Hi Andrew
A late respone because of my holliday.
This is not the case, the flow conditions are always true and it sets a flag when row is processed, so the row is not show up in the query at next run.
The problem is that not all rows is picked up bij de process flow.
Robin.
+23Hi Robin,
Perhaps try using the Run Once option in the scheduling. My understanding is you have a lot of records to update which may mean processing until the next run iteration which may conflict.
Run Once means to define a record to avoid this specific process flow from executing on the specific document or object again the next time it runs.
To avoid long runs as scheduling is about 5-10 minutes apart, perhaps with that type of schedule, you can define the selection to only pick up the top 50 or 100 rows so those are processed more quickly and then the next run picks up the next set? Selecting 1000 to 3000 records most likely takes longer to process per record as it is a larger dataset to manage then selecting 50-100 records.
Hi,
It seems the issue was that I had multiple conditions without any actions when the condition was true.
The condition I used was a query that checked if the order was in the ap_lock table. If it was, the process would do nothing.
I have removed this condition and added it to the Data Query instead, and now all rows are processing correctly.
As I’m writing this, I’m thinking that maybe I could change the condition to: if the order ID is not in the ap_lock table, then perform the action; otherwise, end the process flow.
But everything is working fine for now.
Robin
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
