Resolving flow errors the 'retrying errors' has been spinning for hours
Resolving flow errors the 'retrying errors' has been spinning for hours. Is there a way to restart it? I know it is browser based so I tried using task manager with no luck. This could be an obvious answer to sorry in advanced :)
0
Comments
Hi Barb Downey, you can try refreshing the page. Refreshing the page won't interupt the flow itself.
Tom
Thanks Tom! I didn't have to. I went back in later and it had refreshed. I think I summited more than I thought I did and it was just doing it's job LOL. Appreciate the response.
Tom, I have over 130,000+ errors and it expects me to "resolve" 1000 at a time. I need to stop the retries at once, how can I achieve that?
Hi John Esraelo,
You can cancel a job that's running from the actions column of the dashboard, but if the flow has already run and you have 130,000 errors. It's probably best to determine the source of the errors, fix the problem, and then run the flow again. Have you determined the cause of the errors?
The cause has been determined, fixed, and the retries are still going. That is my concern; how to cancel the retries, canceling the job did not stop the retries. Had taken over 4 hours, finally, it stopped and currently, I am rerunning the process.
thx anyway :)
The process seems to be not so reliable at times.. and retrying the same 130k+ records that once were partially successful after clearing the issue at the destination!
see error
Hello John,
I apologize for your inconvenience, currently, we don't have any easy way to cancel Retry Run. Currently, we are working on it and we will release it in one of the upcoming releases.
For this other issue, it seems like a connection issue with your destination application. If this issue still exists I would recommend you submit a ticket so that our team can look into it in detail.
Regards,
Akhilesh Goyal
Thank you for the reply, Akhilesh!
I had another run that had 13k records, imported 2700, then issued the same "intermittent" error message!
I will have to check / audit the logs and see what's going on.
Please sign in to leave a comment.