Hey
@Jacob Blanco - are you seeing this in the UI? This could be caused by your user preference in the UI being set to your local timezone instead of UTC (which is purely a display preference and doesn’t affect the scheduling logic).
Otherwise, the only way to inform Cloud of a preferred timezone is by providing a timezone-aware
start_time
to your schedule / clocks - the default is UTC though