My goal is to ensure that messages aren’t being lost whenever the trigger subscription service fails for whatever reason. From a monitoring perspective, I was hoping that messages get queued up for retry. I’m manually handling this by invoking the suggested service, “throwExceptionForRetry”. I forced the trigger service to fail which goes to the catch block. The catch block calls the “throwExceptionForRetry”. Another message get published. When I look at Command Central for the subscription service, I don’t see any “Outstanding Events”. I thought the “throwExceptionForRetry” kinda throw the message back to the queue.

I think I got it. It’s a combination of setting the trigger service properties to deal with transient error and updating the subscription service to perform a retry or not. Looks like it’s working as I expected it.