Designer/Gallery: If on tool, wait 5 seconds, then rerun tool

Question

In my continuation of resolving the following 'Output Data Error' associated with saving multiple tabs to a single excel file on a shared drive. I am looking for a way to rerun a single tool (Not the whole workflow) on the condition of a specified error.

Output Error: The process cannot access the file because it is being used by another process. (32)

I've resolved the error occurring when running the workflow on the designer, however, the gallery works differently and I need a solution.

Is there a way to have an error log output from a tool to accomplish something like this?

If <Specified Error> on tool, wait 5 seconds, then rerun tool with cached data. Attempt X times

Honestly, I think this logic needs to built into the Stock Output Data Tool. The pervasiveness of this error in my workflows since the 2022.1 upgrade has put some burden back on me to run workflows that I built for other users on the gallery. Which defeats the purpose of Alteryx all together for me.

geraldo · Answer

@PeteLacz

The block until done bindings are all on the same channel. Isti is not correct.
An output for recording the file
in 2 fly connect to continue the execution in all

Gabacho · Answer

We just had our system upgraded to 2022.1 and I have run into the same issue.  I have tried to convert to batch macros, iterative macro, (this has it's own rediculous error), 'Wait a second, Crew macros. block until done................. Nothing works.

PeteLacz · Answer

@davidskaife I'll ask our Alteryx Admin if Crew macros can or need to be uploaded into the gallery for us. My understanding was always that the CREW macros would get uploaded along with whatever workflow I was saving, so long as I ensured it was selected under 'Workflow Options>Manage Workflow Assets"

That said, even using the CREW macro for Parallel block until done in the designer had failures. So I'm not optimistic it would work better in the gallery. But I'm all for retesting it.

I had No issues with this in version 2021. So Something changed in 2022.1 and to my knowledge no one has been able to pin point it yet