[409] Error after scenario completion

[Tomoh]

I’ve created a scenario to automatically create/copy folders with documents to be shared with clients.
The scenario runs just fine and does everything I expect, except one of the modules returns error [409] after the scenario has been completed. I know for a fact that the name does not already exist until the module generating the error itself creates it.
Screenshots show the scenario in progress with the module completing without errors and then with the error after the scenario is completed.

Also, I used the exact same modules and methods for the other route and it has not caused any errors.
How can a module fail retroactively?
Does anyone know what could be causing the error and how to solve it?

Thank you in advance.

[Stoyan_Vatov]

Hi Tomoh,

it looks like the Search module has returned more than one bundle. So the scenario runs fine on the first bundle, but on the second - the name is already taken. You need to either filter it better so only one bundle is returned, or change your naming convention so its unique for each bundle.

[Tomoh]

Thank you Stoyan, you are absolutely correct.
Issue solved, much appreciated.