Catching nodes that takes too long or never completes

While KNIME is typically quite stable, we regularly have situations were nodes never complete. This could be External Tool Nodes or most typically DB Reader Nodes accessing remote databases (most of the databases we are using are cloud based today and thus “remote”).

Very often the situation may be easily handled by backing up a step and retrying. However, today this must be done manually as we have not found a way to create a kind of timeout error that we could catch in the workflow.

Is there any clever way to do this?