I’ve encountered 2 race conditions today. #1 I’ve had a kinetic-function calling and getting a string. I then used a row-update to grab {actionResult.returnObj} and put that in a dataview. (Both hung on and off the success branch) It would not do it. Debug showed it was in the actionResult data…

For some more context, I believe this is entirely down to the Kinetic Functions reporting success, when they have not completed their actions. I moved my event-next to after my functions returned on my dataset based ones, and did the row-find, row-current-set, and console-write all in line, and it …

Yes. Success branch is queued on response received but actionResult hydration is late and row-update eval is early. This should be well documented but is not, AFAIK. I believe row-update is intentionally eager. Values are immediately evaluated then the action is queued. Meanwhile actionResult is st…

[image] The way I fixed an event in Application Studio was to use a slide-out message Kinetic ERP I was following this guide on “ Passing values to app-open tile ,” and that worked great. So then I wanted to disable a panel card grid after that. I spent a few days off and o…

I’ve had some timing issues before as well, but I think it was things not behaving well during the loading phase. Will probably never be documented.

[image] JasonMcD: I believe this is similar to your post. I do believe you are correct. I have a couple of tests to run today to see why I haven’t encountered this before.

I created a BPM that calls a BPM form giving the user the option to cancel or proceed on Post in costing WB. The kinetic form would send the toast popup that it was posted even when it was canceled… Similar issue where it reads as a success even when it was not. [image] So, I created an event i…

Further analysis of row-update shows it’s not a timing thing. I think the erp-function action drops returnObj is it’s of type object. processRestResponse(s) { if (!s || !s.length) return; const r = s[0].result.result; this.processParameterResponse(r), this.processReturnObjR…

[image] jbooker: Further analysis of row-update shows it’s not a timing thing. No, if there is a delay, it works, so it is timing. And same behavior if using a different output parameter.

Yeah I think you’re right a delay helps because of a likely async commit gap between processRestReponse > trans.set(…) and what trans.get(…) sees when Row-Update runs. :thinking: OR maybe current row isn’t yet set on actionResult. What do you get with this immediate console-log in success branch? …

[image] jbooker: What do you get with this immediate console-log in success branch? -1 before function -1 immediately after run again 0 then 0, because it has a row, and has advanced

Wild Race Conditions in Kinetic - Anyone seen this?

Kinetic ERP

JasonMcD (Jason McDermott) April 24, 2026, 11:07am 4

I believe this is similar to your post. Honestly there were a lot of words so I may be on a tangent here…