Why does my integration run twice or create duplicate items?

Short answer: Sending an item back and resubmitting it fires step triggers again. Add a flag field and a condition so the create action runs only once.

Why it happens

• When an item is sent back and resubmitted, triggers such as When an item enters this step and When an item is about to enter the step fire again.
• When API load is high, runs can wait in a queue and execute later than the event that triggered them.
• A duplicated action or integration can carry stale configuration that causes duplicate calls, for example an HTTP POST action that runs more than once.

How to fix it

To stop repeat runs after a send-back:

1. Add a text field to the form to use as a flag.
2. Create a second integration with the When an item is sent back trigger.
3. In that integration, write a dummy value into the flag field.
4. In the original integration, add a condition to Create and submit a new item so it runs only while the flag is empty.

A variant: after the create step, add an Update an item action on the same process that resets a Yes/No trigger field to "No". The item then won't create again.

If a duplicated action makes duplicate calls:

1. Click Refresh fields on the action and check its mappings, or delete it.
2. Add a fresh action instead of a copy. A copied action keeps the original's full configuration.

If Auto retry is on, a retried step runs again after a temporary failure, which can send a second email or create a second item. Turn it off for integrations where a repeat isn't safe.

If a run seems to happen on its own after the item is complete:

1. Check the trigger configuration. Such runs can be rare delays caused by queueing.
2. If the trigger is a webhook, remember it runs only when something calls its URL. Check which external system is calling it.

To see which runs happened and which actions ran or were skipped, open Run history in managing integrations.