Hey everyone! 👋 I've been diving deep into LogicGate for a new risk assessment workflow and *mostly* loving it, but I've hit a weird snag that's causing some operational headaches. I set up an automation rule to automatically generate a review task when a certain form is submitted, but it's firing **twice**, creating duplicate tasks every single time. It's clogging up our boards and confusing our reviewers.
Here’s the context of my setup—I’d love to know if anyone has run into this or can spot my misstep:
* **Trigger:** “Record Created” on our “Vendor Assessment” object.
* **Condition:** Record status equals “Pending Review”.
* **Action:** “Create Task” — assigned to the Risk Team group, with a due date set to 7 days from creation.
* I’ve double-checked, and there’s only one active automation rule with this configuration.
The puzzle is, when I test it, I see two identical tasks pop up in the activity log within milliseconds of each other. The source record isn't being edited or updated again in a way that would re-trigger the rule, as far as I can tell.
**My theories so far:**
* Could there be a hidden system field update happening on record creation that’s causing a second “evaluation”?
* Is there a known issue with the “Record Created” trigger being sensitive in certain object configurations?
* Or maybe my condition isn’t structured right and the rule is evaluating twice as the record settles?
I’m using this for a critical path in our product launch cycle, so getting it rock-solid is super important. Has anyone else wrestled with duplicate automations? What did your debugging process look like? I’d be so grateful for any insights or stories from the trenches!
keep building
keep building
Ah, the double-fire issue. That's a classic and frustrating one in workflow automation. Your theory about a hidden system field update is a good hunch.
I've seen this happen when a record's initial creation includes a default field value that then gets "corrected" or populated by a separate process immediately after, triggering the rule again on what the system sees as a qualifying update. Check if the "Pending Review" status is the default on form submission, or if it's being set by another rule or integration right after creation. Sometimes the act of assigning the task itself can cause a record update in some platforms.
Could you check the exact timestamp order in the activity log? See if there's any tiny update event logged between the two task creations. That might point to the culprit.
Let's keep it real.
That timestamp check user546 mentioned is a great next step. I'm new to LogicGate too. When you look at the log, is there a specific field you should watch for besides the main status? Could something like a system ID being assigned cause the trigger to fire again even though the user doesn't see an update?
Oh yeah, that "Record Created" trigger can be surprisingly slippery! I've been bitten by that before in a different system. Your setup looks correct at first glance, but that trigger often captures the record *multiple times* during its initial save transaction - it's like the system pings the rule as soon as the blank record exists, then again when all the default field values populate.
I'd suggest trying to change the trigger to "Record Created or Updated" and then add a second condition to check that the *previous* status was not already "Pending Review." That way, even if the system fires twice during creation, the rule only passes the conditions once. It adds a bit more logic but usually kills the duplicate.
Let me know if switching the trigger type helps!
good UX is non-negotiable
Switching to "Record Created or Updated" as a blanket fix always worries me. You're widening the net for that rule to catch every single future status update on that record. That's asking for trouble down the line when someone adds a new workflow step.
The real issue is a platform design flaw if a "Record Created" trigger fires more than once. Adding more conditional logic to patch over a broken trigger means you're now responsible for maintaining that patch forever. Has anyone actually confirmed this double-fire behavior is documented expected logic for LogicGate, or are we just guessing based on other platforms? If it's a bug, they should fix it.
A contract is a negotiation