Describe the issue
We intend to use a rest-hook subscription in R4 (HAPI 7.0.2 using JPA) to notify when any resource of a given type is created/updated.
To do this, our subscription looks like this:
{ "resourceType": "Subscription", "status": "requested", "criteria": "[Organization]", "channel": { "type": "rest-hook", "endpoint": "http://fhir-subscription-handler.ci-hapistuff.svc:8080/notify", "payload": "application/json" } }
If that endpoint is down, it appears that HAPI tries for almost exactly 1 minute, before throwing a final failure exception and not trying anymore for that Notification.
Is there any way to get HAPI to try for longer, or indefinitely?
Having missing Notifications is a bit of a red line for our solution.
According to Smile CDR docs here "Subscriptions that fail to deliver to their specified channel will retry on error. By default, they will continue to retry indefinitely until they succeed"
Describe the issue We intend to use a rest-hook subscription in R4 (HAPI 7.0.2 using JPA) to notify when any resource of a given type is created/updated. To do this, our subscription looks like this:
{ "resourceType": "Subscription", "status": "requested", "criteria": "[Organization]", "channel": { "type": "rest-hook", "endpoint": "http://fhir-subscription-handler.ci-hapistuff.svc:8080/notify", "payload": "application/json" } }If that endpoint is down, it appears that HAPI tries for almost exactly 1 minute, before throwing a final failure exception and not trying anymore for that Notification.Is there any way to get HAPI to try for longer, or indefinitely? Having missing Notifications is a bit of a red line for our solution.
According to Smile CDR docs here "Subscriptions that fail to deliver to their specified channel will retry on error. By default, they will continue to retry indefinitely until they succeed"
Can we get the same behaviour in HAPI?