Hi, We have automated process that run for each request that has come

What type of technical issues are you experiencing? We do something similar for Query DB nodes that rely on external databases which sometimes go down. These nodes are configured to continue on error and wait at a Receive Message node. In this situation, we do receive multiple emails (hundreds usually), but all processes are started with one click of an admin process that sends messages to all waiting nodes. In this case you could also update a constant on the first error and pause all processing at a Rule node - then flip the constant back once the issue is resolved. Maybe that will give you a few ideas, depends on your use case though.

What type of technical issues are you experiencing? We do something similar for Query DB nodes that rely on external databases which sometimes go down. These nodes are configured to continue on error and wait at a Receive Message node. In this situation, we do receive multiple emails (hundreds usually), but all processes are started with one click of an admin process that sends messages to all waiting nodes. In this case you could also update a constant on the first error and pause all processing at a Rule node - then flip the constant back once the issue is resolved. Maybe that will give you a few ideas, depends on your use case though.