hi,
I am using API call to retrieve some information from another website. It can retrieve the data correctly, but when I try to save this data, e.g. copy to another table, I will get inconsistency.
When I first launch the app, the correct information is copied, BUT subsequent API calls, the information copied seems to always be the information of the previous API call.
Below screencapture is what the flow looks like and information shown on the screen is as expected. Only issue is when I want to capture the information to another table. The payment link, I need to actually use directly from this column for it to work as when I copy, it will also likely copy the previous call.

Suggestions please.
TQ
Any chance you are writing the information to the other table before the API has returned the newest result? What’s your flow like to copy it to another table?
thanks Jeff.
My flow as below:
- Call API is setup via column in Glide table. Setup the variables for Call API. Once the variable columns are populated, the call API auto-starts.
- Wait 12 seconds for two items, website link and reference number to be available. I choose 12 seconds as I remember it takes 10 seconds for the app to refresh and adding buffer.
The routine will exit with error message if two items are not not available (check for not empty condition). JSON Query is used to extract these two items.
- The website link is open with web embed. this is always successful when I use the link directly from the JSON query column. If I try to copy by add row or column set, the copied link is always from the previous session of API call. As mentioned from previous message, upon opening the app, the copy is always correct.
- From your comments, I tried adding an extra 20 seconds before adding row or set column. The result is still the same, i.e. the residual still copied, even though,
a) I can see from table that the new variables appear and
b) I can go to the new link with direct access to JSON Query column of website link.
Let me know if there is something else to test. Or is there better flow to achieve the desired result.
TQ
Hmm, not sure then. My only thought was to incorporate wait timers, but it seems like you are already doing that.
1 Like
Do you display the API result anywhere on the screen where you house the component that has that action?
1 Like
yes, but that happened while I was doing lookup to try and figure why I kept getting the previous version. after debugging a couple of days, it is related to when the info comes back from API call.
FYI that I managed to solve by re-doing the logic to not use the copy function. This resolves the timing issue. I add a row for every time I use the call API. This ensures that the returned URL is always available to allow the system to look up that row and then make a copy of URL.
Thanks both @ThinhDinh & @Jeff_Hager
2 Likes