Hello,
Does anyone have problems with Cloud Workflow creating folders with (2) at the end when routing a document? I can run the document through the same workflow afterwards, and it'll end up in the proper folder - not the duplicate. This happens enough across my different Cloud accounts that I've never been able to pin it on anything. Any ideas?
Question
Question
Cloud - Workflow - duplicate folders getting created
Replies
Presumably the "(2)" is auto-applied because there is already an entry in the folder with the desired name. Have you looked though the audit logs to see when the first one is created and what happens to it?
Yes, the folder that the document is getting routed to already exists, but sometimes Workflow will create a new folder with the same name (with the (2) at the end) and put the document there.
For example, a document has a Date field, and a workflow routes the document to a \%Year\%Month\ folder. The 2024\09. September\ folder already exists (created by this same workflow earlier), but Workflow will put a document in a \2024\09. September (2)\ folder instead. It's usually just one document in this extra folder - that's all I ever see when I find these folders.
were you able to resolve your issue?
I am having this issue too, my workflow creates a duplicate folder instead of routing to the folder it is supposed to
I've never been able to. It maybe doesn't happen as often as it used to, but it's still pretty common for me to look at an issue with a customer and stumble upon folders with the (2) at the end of the name that just contain one document.
What I've done is schedule workflows to run prior to whenever these folders would get created, and create the folder with the scheduled workflow instead. If the folder already exists, it won't create the duplicate.
For example, I have a customer who stores documents in a \%Year\%Month\%Day\ structure. The %Day token would come from today's date, so every day, there's a workflow that creates the \%Day\ folder for the next day. The duplicate folder never appears when doing it this way.
A fix for this issue was deployed in early May. If you are still running into it, please open a case with Tech Support and provide information on the workflow instances where you are still seeing it.