Hi @mohdriyaz , It seems the generatetablefetch by design pushes and penalize the flow to the upstream queue when there is an error that is considered none "sql query" error which per documentation only query execution error will go to the failure rel. It doesnt seem like there is anything you can do to change this behavior. The only thing I can think of to mitigate this issue is by adding another processor as a guard to help checking the connection status before calling the generateTableFetch processor. For example you can use PutSQL processors which seems from the description able to capture connectivity error through retry & maybe the failure rel per description: This is not going to solve the problem 100% but it will minimize it and it will help you capture the error. You can configure how many to retry and for how long in the relationship tab once you select to retry. Hope that helps. If it does help please accept the solution. S
... View more
