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.
For automatic subscriptions that are triggered by
Data Integration Hub
, you can define a retry policy.
A retry 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.
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.