I have a flow designer in which I am updating the time zone with location.timezone if the location is not empty and trigger condition is Record created or updated.
The flow is currently triggered on Record Created OR Updated, which causes it to run even when the Location field is empty.
As a result, unnecessary entries are being inserted into the sys_flow_context table.
Also, I could see the flow logs twice for the same user record in PROD instance and I couldn't replicate this issue in non-PROD.
When I verified the logs, I found in both logs the if condition also executed and update happens twice. How can be the update happen twice in the same timestamp for a particular user.
What could be the reason for this?
did the flow run 2 times because of multiple updates on same record?
any business rule or script include is updating the record 2 times?
you are not able to replicate in lower instance may be because PROD will have lot of integrations which might be updating the record and leading to flow triggering multiple times
See by adding the Trigger -> For Each Unique Change
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
I have already added the trigger as Trigger -> For Each Unique Change.
This is newly added flow creates a log, even if the location is empty like below
Is this the expected behaviour?
I have modified the trigger condition as below in the flow to avoid the logs created in the flow_context table.
Even then it creates the log but it doesn't execute(update) the condition since the location is empty.
sys_flow_context :
Is this the expected behaviour?
