If a pipeline creates records, sooner or later it will run twice for the same thing. An edit re-fires the trigger, someone ticks a checkbox again, a step gets rerun. With Create Record, every extra run adds another copy.
The fix is to give each record a key that says what it is, and write with upsert instead of create.
[Inspection Record ID#] & "-" & [Checklist Item Record ID#]Add a Text field for that key on the table the pipeline writes to and check Unique in its properties. Now Quickbase won’t accept a second record with the same key, even if something is misconfigured.
Then replace Create Record with the Bulk Record Sets steps: Prepare Bulk Record Upsert with the key field as the merge field, Add a Bulk Upsert Row inside your loop, and Commit Upsert after it. If the key already exists the row is updated, otherwise it’s created.
One thing to watch: an upsert overwrites every field you map. If people edit those records by hand afterward, only map the fields the pipeline owns.
It’s also worth tightening the trigger so it doesn’t fire on every edit, but the Unique key is what makes a rerun harmless.
I wrote up the full version, including checkbox triggers and the JSON API equivalent, here: https://www.topstep.tech/blog/quickbase-pipelines-prevent-duplicate-records