'Make changes to a thing' runs but does not persist changes in database – possible outage issue?

Bugs
1

I’m currently experiencing an issue where “Make changes to a thing” actions are not actually saving to the database.

I’ve already checked the following:

  • Used the browser Inspect/Network tab to confirm the workflow is triggering.

  • Checked server logs, and the action appears to run successfully.

  • The workflow shows the “Make changes to a thing” step executing.

However, the changes are not reflected in the database afterward. The values remain the same as before the workflow ran.

Given the current outage notice affecting AWS zones in me-central-1, I’m wondering if this could be related to the infrastructure issue. Has anyone else experienced a similar problem where workflows execute but the database doesn’t persist the changes?

Thanks in advance for any insights.

2

Have you used the debugger to check the thing you’re changing? Have you verified the user’s privacy rules permit them to access the Thing?

3

Yes, The debugger shows the thing I’m supposed to be changing. No Privacy rule limits access to the thing

4

Has happened before to me, I took tips from here:

I believe for me it was solved by using Custom Events, some sort of order of operations issue. It bit my brain off for like a day when I was dealing with it.

5

This topic was automatically closed after 14 days. New replies are no longer allowed.