Often I am reading a field in a consecutive action that I filled in the previous.
And often the content that is written to that field in Airtable is not “available” yet for the follow up action and therefore the old value gets read/used.
I presume that if there were a “time out” or “pause” element that I could add into the action flow, I could give the data time to be written.
One useful work around would also be expanding the utility fields to include cache fields that I can write information into and then read that data back in consecutive steps
I would like to re-address this as it really causing us trouble and cumbersome work arounds.
We tried to temporarily write data to a field that we created in Noloco iteself in the hopes the data would be written faster to the internal Noloco server than to Airtable, but this is not the case.
The action button sequence is faster than the data being written.