Ability to access the schedule's id at runtime
I’d like to expose the ID of the currently executing schedule (if the flow is triggered by a schedule) as a global-defined variable (like the ones listed in https://support.etlworks.com/hc/en-us/articles/360016579573-Default-variables).
Use case:
This would make it easier to build flows that can adjust behavior dynamically based on the schedule that triggered them. It would also reduce the need for hardcoding or manually simulating schedule behavior during testing and development.
In particular, when a flow is manipulating schedule-related data, and there’s no way to programmatically exclude the schedule that triggered it, there’s a risk of unintentionally altering the very schedule that’s running. While this could be avoided by hardcoding the schedule ID, that approach doesn’t scale well or work cleanly across environments.
Having access to the schedule ID at runtime would improve safety, flexibility, and portability of schedule-based flows.
Comments: 1
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
22 Sep, '25
Olena Sherbinin AdminHighlighted comment
Implemented in 8.1.5
https://support.etlworks.com/hc/en-us/articles/360016579573-Default-variables#ScheduleID