Robustness of references to things stored in database

Need help Database
1

Does anyone encounter intermittent issues on references to things not being stored robustly?

I ran an backend API workflow to populate a field (of type Thing) in ~30K things, by “doing a search for” in another data type. 4 records did not get populated. I later manually found and populated them with no issue.

I have no idea why the API workflow didn’t find them in the first place. Maybe a glitch during the database search?

This is the 2nd time such an incident occurred.

Anyone encountered the same?

P.S. I also discovered that if I have references to things in my data type, I cannot do a “copy from development to live” as this would wipe out all the references. Seems like the unique IDs between test and live are different in such a copy operation. Are there any best practices when it comes to having references to things?

3

Thanks, omg that sounds serious if that’s true. How are they not even fixing it…

5

I see, that’s new to me…

But actually I was using the “Bulk Operation - run API workflow on all the entries”. I thought it already spread out the calls. Even this doesn’t work robustly hmm.

Now I’m wondering if sometimes fields don’t get populated is due to this lol.

7

Nope, I was using the “Bulk operation”, and running an API workflow on 30K things.

image
image1466×514 26.1 KB

9

Oh ok, that’s somewhat of a relief to hear :smiley:

Yeah it’s always the references to other things that are problematic.