My workflow is triggered when file appears in a Google Drive folder. However it fails sometimes due to 3rd party service llamaparse, which is out of service sometimes. What I would like to do is to re-run the workflow when this happens after some significant delay like 30 minutes. However the workflow is never triggered again for the file, which was already uploaded.
Hi Mohamed, thanks for a quick reply! Thatās an interesting idea and Iāve implemented that for the PDF upload node I had problem with today.
However I would still prefer some more foolproof solution. What I mean is that there are a lot of other nodes, which can fail (the workflow I posted is just a subset of the full one) and I donāt want to implement a wait cycle to each. I would prefer the whole workflow to fail and be re-run later.
Something like: Check Google Folder every X minutes and if there are files, process them. Currently it only processes them once because it picks the new files from the last check.
Also isnāt there some workflow runtime limit I would hit with wait nodes waiting for 30 minutes?
Maybe you could redesign the workflow so that in case of failure, the file is moved to a āfailure folder.ā Then, set up another workflow that triggers every 30 minutes to move the file from the āfailure folderā back to the main workflow folder, thereby restarting the processā¦
