Hello! We have a flow that gets triggered every time a new case is created in Salesforce. So it runs one time for each case with the node “CaseCreated”. It run fine for months, but since yesterday it started running multiple times for every case, every time a case is updated.
Any idea what changed?
Thank you!
good morning @AthinaN
did you check the Salesforce side? is the trigger set for creation or creation/update?
i would add a filter right after the trigger to continue only when the record is actually new, for example by comparing CreatedDate and LastModifiedDate or saving the already processed CaseId in a Data Table/DB to ignore duplicates.
Hi Tamy, thank you for your response!
The n8n flow should get triggered on case created, but since a few days ago it started to get triggered on every case update too. The Salesforce flows run as expected.
I have a filter, just like you said, to prevent the “update” runs, but I would like to figure out why this is happening. Because there are a lot of tokens spent now for no reason.
@AthinaN
I would compare the raw payload of an actual creation event with an event triggered by an update. Since this changed without any workflow modification, it could be a change in the event sent by Salesforce or in how n8n interprets the trigger. To reduce tokens, keep the filter before any AI nodes. Could you please share the JSON and setup if you still can’t find the solution?
Did you update n8n to the stable version 2.20.8?
There was a bug with the Update nodes that fired only once per instance and it was fixed and they now run for every update. I’m thinking maybe this changed something in the Creation nodes. Salesforce Trigger fires only once for repeated Account updates · Issue #21028 · n8n-io/n8n · GitHub
Could it be related to that?
good morning @AthinaN
The images help, but I would still confirm one key point: are these separate executions in the n8n history or the same execution continuing? If they are separate executions, and the Case ID + CreatedDate are the same but only the LastModifiedDate changes, then it looks like a Case update is triggering the “Case Created” trigger. To isolate this, I would test a minimal workflow: Salesforce Trigger (Case Created) → NoOp, without any “Update a case” node. If it still fires on updates, then the suspicion of a regression in Salesforce becomes much stronger.
Hello Tammy!
They are different executions. Exactly, it looks like a Case update is triggering the “Case Created” node. Find some more screenshots below.
When testing with the simple flow now, I created a case and the flow ran. Then I updated the case and the flow ran again with every update. So it confirms the theory.
But when I updated other cases that were already created earlier, sometimes it ran and sometimes not.
It’s confusing!
@AthinaN
The most likely explanation would be state/polling cursor behavior or the Salesforce Trigger internally using LastModifiedDate instead of filtering strictly by CreatedDate.
Can you share an example using the same Case Id, showing CreatedDate, LastModifiedDate and the execution times in n8n? If the CreatedDate is old, but the “Case Created” trigger executes again after only changes to LastModifiedDate, this would be a strong indicator that the trigger is reprocessing updated records instead of just new Cases. In the meantime, I would keep a defensive filter in the workflow comparing CreatedDate and LastModifiedDate to avoid spending tokens/processing on updates that shouldn’t trigger the flow.
Hi Tammy, really appreciated your support on this one.
It was a bug actually, they have fixed it and waiting for the release.
Thank you! Have a great weekend ahead!
I’m the one who should thank you for sharing, and have a great weekend as well.
