This is the issue I have previously created a post about, but it keeps comming back - even if I use different approach.
I have a JSON response that has unique id and 3 values. It can have up to 900 items (sets of unique ids and values), values can be 0s but aren’t nulls.
I tried to make changes to things that have the following unique id in 2 ways:
-
I have build a loop that was scheduled on unique id in text form and 3 number values and it later adjusted every item and deleted first item from the list.
-
I have built a run workflow on a list and adjusted the endpoint - so now it doesn’t return all items, but first we collect all unique ids and then I do a call one by one for each item get their values.
What is the issue:
Using both methods, and I have build logs, great logs ( like a president would say) and they show that when I pass the values to a run on a list workflow - the items somehow disappear. I start the workflow on 900 elements and somehow after the first step I already see only half of the records.
We cannot have unique id’s that are not in my app, as there is no hard delete, so something is fishy.
Same issue I encountered while running a loop - as it took correct activities but somehow broke the numbers that were assigned in the JSON object list.
Anybody has some good practices what to avoid while doing workflows like this one? Or what are the common issues that people can encounter? This is another attempt to parse a large list of data and match them to database and whenever I touch this task, I always encounter many obstacles.