Lukas,
When you save the data are you selecting either Yes or Yes without events in the Commit section of your Create / Commit action?
Hi Lukas
Can you share your logic? I suspect that after commiting the object maybe due to any error does the actions/microflow would be rolled back using error handling. But without seeing the logic it is difficult for us to guide.
Hello,
You might be updating an object in your Microflow, but the changes are never being saved to the database. This can happen if you're using a Change Object activity without a subsequent Commit Object, or if the commit configuration isn't set up as expected.Make sure the Microflow includes an explicit Commit Object(s) activity after making changes
Check with the entity access of the Entity. If the access is not given this might be also one issue.
Check if there is any error appearing before the microflow transaction completed.
Accept this answer if you find this has given you a solution
Another possibility is that your microflow does not commit the object but, it does commit another object that references the first object. The first object is then temporary saved to the database (autocommit). You have to commit the first object explicitly, otherwise it will be removed from the database when the session ends. In that case you should see a warning in the logging.