- Time-based: The scheduled pipeline runs at defined intervals.
- File arrival or change: The scheduled pipeline runs only if a file arrives or changes.
Time-based trigger
Frequency
Time-based trigger configurations vary according to the frequency of the trigger. The following sections describe the parameters needed for each frequency.When using time-based triggers, the default timezone is the timezone from where you access
Prophecy.
Minute
Hourly
Daily
Weekly
Monthly
Yearly
File arrival or change trigger
Use this trigger type to run a scheduled pipeline only when a new file is added or an existing file changes in a specified directory.Trigger configuration
Each trigger configuration defines where and how Prophecy detects file changes. Provide the following:Add multiple trigger configurations
You can define multiple trigger configurations to monitor more than one location for file updates. Use AND or OR logic to control when the pipeline runs.- AND: All conditions must be met before the pipeline runs.
- OR: Any one condition must be met to trigger the pipeline.
- With AND logic, the pipeline runs when a change is detected for both Transactions and Exchange Rates.
- With OR logic, the pipeline runs when a change is detected in either Transactions or Exchange Rates.
Advanced settings
These advanced settings determine how the poll-based data sensors work. For additional details, jump to the following sections.Poke Interval
The Poke Interval specifies how frequently the sensor checks for file updates, such as new files appearing or existing files changing. The default interval is 60 seconds.Sensor Timeout
The Sensor Timeout value determines the maximum amount of time the sensor continues to check for file updates. By default, the sensor runs indefinitely. Set a timeout only if there’s a point at which you know the check is no longer useful or relevant.Exponential Backoff Retry
Sometimes, the sensor does not detect any file updates when it checks the directory. When Exponential Backoff Retry is enabled, the wait time between checks increases every time the sensor must retry the operation after failure (no file updated). When active, the delay between each polling attempt increases exponentially—e.g., 60 seconds, 2 minutes, 4 minutes, 8 minutes—while adding randomness (jitter) to avoid system-wide contention. This option is enabled by default to reduce system load.Poll Mode
Choose between the following modes:- Poke: Keeps resources active between checks. Best for short intervals when quick response times are needed.
- Reschedule: Frees resources and reschedules itself after each interval. Recommended for long intervals to reduce resource usage.