Suggestions for using data before it can be read? (database saving latency)

Much of my recent frustrations come from things that don’t happen properly because I try to do a follow-up action based on the results of an action… BUT it fails or doesn’t work properly because the data is not yet available. I’m only assuming that it’s database latency, but I don’t really know why. For example, data is written to the database and needs to be recalled right away, but comes up empty because it isn’t finished writing to the database… maybe? I’ll ask my question (below) and then give a couple examples.

Does anyone have any suggestions for working around this?

Scenario 1: User signup action on a button, including saving a random code to the user collection. Then I want to do something with that new user data (in this case, send out a validation email via sendgrid api). But when the next action runs, it doesn’t have many or all of the new data that was just saved. But if I refresh the page, suddenly the new info is available.

Scenario 2: Adding a new record to collection A, but also want to create a new record in collection B. Sometimes, not always, the new item in collection B doesn’t get written right because it’s missing something… presumably because it was trying to read data that hadn’t been written yet.

This type of thing is super frustrating and makes it difficult to create useful but complex functionality. I was hoping the community might know of workarounds. I budget an hour for some of these tasks and end up spending the better part of a weekend trying alternatives because the platform isn’t working the way it’s supposed to. Help!

Regarding the first issue, if you are trying this on web it might be a caching issue since I have noticed similar behavior sometimes, but once built to a native app things works well

Thank you. But this is not ideal. Nowhere does it tell me that newly created data can be delayed due to caches. Nor does it give me an option to opt out of the cache for that operation. What it DOES do is give me a nice clean interface for instantly doing something with the “new whatever” all in the same action/click as the one that created the “new whatever”.

Therefore, if it’s not allowing this to succeed, then it is a bug. Would you agree?
Can someone from Adalo chime in on this?

What can be affected by the caching is displaying the latest data on the screen on web, but the sequential actions should work properly regardless of that

In my apps I use the same scenario without issues, creating a new record and working on its data on the same action is not a problem

Perhaps you can post some screenshots of the action so someone can notice any issue with the flow

Thank you. I will try to find a clear case and then capture some shots of it. Thanks!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.