Are there any workarounds for that, please? Or maybe plugins?
My issue is that I do this search in backend workflows, so no chance of using page elements.
I have a thought of random number generation with max of count(prompts) and iterating to make a list until N, but this is so much overkill I cannot even imagine something more
Gens_amount dynamic (from 1 to 25), options for each sex starts from 20+ count. So it’s not like they are accidentally repeated by chance. I’ve tried multiple times with different gens_amount values.
I’m aware of double sorting, was just showing that neither of them works.
Have to make an API call to your own app with the current timestamp (so each call is unique and doesn’t cache the same API response) and other relevant search constraints. The backend does the random search with constraints and returns the unique ID of the thing. You use that response as constraint unique id = response's unique id in a search for that same datatype
Hi Tyler - I’ve just given this a shot and unfortunately it didn’t work for me.
Using an API call and passed the current timestamp successfully, but I’m still getting the same unique id every time, despite the list being random. Very frustrating
Yeah, I have to add that moving this to Backend Workflows doesn’t solve the problem - it’s random on the initial call, then it’s cached or something, idk.
Well, right now randomization works perfectly fine for something like select * from table. I guess that’s it. I suppose there was some fix (didn’t check the changelog)
@anon99913292 I’m having the same problem where using “random sorting” when getting a list won’t give a random list, could you explain more in detail what you did to achieve this? I couldn’t quite figure out what you meant in your latest reply. Thanks!
