Hey @nri.scraping
You’ve shared 6 automations with complex workflows and conditionals.
For example this one has 10+ steps and a conditional flow.
And my guess is that the issues are on the logic of the automations themselves.
For instance here you’re tryin to run a conditional on weather the entire column is not empty. This will check over the entire column if there’s any values. Is this what you’re trying to do? Or check over row by row if they contain the value?
If that’s the case, consider using the “get rows from table” command.
Some notes:
-
Consider using “when a googls sheet rows” commands to trigger the autobooks instead of the “scheduled” triggers. Doing this will allow you to check for the data of the row triggered row instead of all the table.
-
Consider using our “update google sheets” command to update information, it’ll make sure you don’t duplicate rows.
How to use Update Google Sheet rows -
We can offer a free consulting session. Schedule it here.
After that, we also have introduced custom consulting if you’re interested, as you can see on our Pricing page.
Or you can also search for a consultant on 
Jobs and Gigs by sharing this post, and have bardeen users reach out.
This considered, I can’t see a clear bug we can reproduce here, since there’s too many actions involved and it can easily be a logic issue.
It might be a process of checking case by case on detail.
And unfortunately, these require much more context and a walkthough on your use-case, since they are not as trivial to fix.
What can we do from here?
If you can record a loom where you can walk us though the use-case, the automation and reproduce how it creates the duplicates, we can take it from there!