Recently, we were experiencing some difficulties while running certain automations. So, we decided to try using the API to send a POST request to create records and update fields within an existing record, triggered by a Tadabase webhook.
Everything was working great until we discovered that 10 minutes after the POST request was executed (with a response code of 200), all the changes that involved a field update automatically rolled back.
Even when we checked the history logs of the record, the last modification was made by the API, and it effectively posted a “Yes” into a specific field. However, this field then reverted to “No” (default condition) without registering the change in the logs.
Has anyone else experienced this issue? If so, how did you resolve it?
Ive never seen that JUST with an API call (but read on…) and I’ve used the API extensively. Out of interest, is there any possibility the API “platform / code” managed to execute a second API call that reverted the record back? Also what happened to the created record, was it remove?
How are you sending the API call and what calls are you using?
One thing to check is that a record rule or web hook isn’t making any updates, do you have any record rules or web hooks that touch these fields that have rolled-back? WEb hooks can fire 10 minutes later so that’s defo one thing to check, Actually I HAVE done something similar myself once, now come to think of it!
We’re using a PowerAutomate flow that catches the webhook, process some data and then the flow does the several POST requests.
Regarding the new records that this flow creates these remain intactly in their tables, but the record that were update just rollup to the previous status. In this case we specially focus un the PowerAutomate? field that indicates that the external flow ends his job
For example:
1-When i create a new record (It shows that the PowerAutomate field is “No”)
2-Then we wait until the PowerAutomate execute (Here shows two logs, when its created and when the flow post an update in the field)
3-And if we see the record at the end it seems that the PowerAutomate? field didnt change but the child records were efectivelly created (Blank Rollup = 20)
If we check the history the logs are the same that in the second photo.
Have you doublechecked that you don’t have any record rules that could be being executed that set the Powerautomate value? (like some initialisation rules that should only fire on Create and not Update and Create for example?)
If not, what if any other scripts or rules touch the Powerautomate field how and what things can set this to No.
The other thing that crosses my mind is whether you have a filter applied to the Tadabase webhook or will it execute every time a record is updated? If you don’t have a filter on this then when Powerautomate flow updates the Powerautomate field to “Yes” it will trigger the webhook to run again, is that happening ?
Lastly, if none of the above applies I suggest you create a new test app and just rebuild the exact same flow on a table with a single field in it and copy your automate flow to simply see if the problem persists. On the occasions I can’t figure out what’s happening I usually try this approach and half the time the problem doesn’t persist so I know it’s not a bug, but something else. If the problem does persist it’s a whole lot easier for the support team to troubleshoot when you’ve narrowed it down this far.
@GREDDIE I think the great problem here is that something is changing the PowerAutomate? Value from Yes to No and there is no track of that change in the record log, unlike the first two operations, creation by form and edited by API to Yes value. If some “hidden” process or rule did that, the log is not tracking the event.
