The subscription schedule defines the frequency of the subscription for subscriptions that are triggered by
Data Integration Hub
.
You can consume published data when it is published, manually, by an external trigger, at defined intervals, or after a specific publication or subscription run completes. If you create a compound subscription, you can only choose to consume data when it is published, manually, or by an external trigger.
Consumption of data by the subscription starts when one of the following conditions exist:
The subscription schedule is set to consumes data immediately after the publisher publishes the data to
Data Integration Hub
.
The scheduled start time arrives.
The developer starts the subscription from a command line API or from a REST API.
You manually run a subscription that is in a Delayed status.
You manually get previous publications.
The running of the publication or subscription after which the current subscription is configured to run is complete.
Retry Policy
To improve business continuity, you can configure a retry policy for subscriptions that are triggered by Data Integration Hub. The policy defines the number of times
Data Integration Hub
retries to run the subscription in case of failure and the retry interval. The policy does not apply to subscriptions that you run manually. You can define a policy of up to nine retry attempts with a retry interval that is between five minutes and 23 hours.
Data Integration Hub
attempts to reprocess subscription events in an Error status based on the policy you define.
Data Integration Hub
doesn't attempt to reprocess Error events in the following scenarios:
You manually change the status of an Error event to Complete.
You manually change the status of an event to Error.
You manually reprocess an Error event and the subscription runs successfully.
You can define a retry policy for automatic subscriptions that are triggered by
Data Integration Hub
.
The policy does not apply to subscriptions that you run manually.
Data-driven subscriptions are not triggered by
Data Integration Hub
. For subscriptions of this type you define the time intervals according to which subscriptions groups and consumes data.