we are using Pub-Sub model for our integration and have the below requirements:
If any transient error(like n/w outage) occur during processing at Subscribe side, Trigger will retry & suspend the trigger document processing and document retrieval and a resource monitoring service starts to check the connectivity status. once, the connection becomes active, it will resume the trigger.
Along with it, we need to send the n/w outage time window to the target system before trigger resume processing. Now, is there any way/logic by which we can determine whether its a n/w outage or DB downtime from the error/exception that IS will throw during transient error.