From 8fed7dc4519f6e7888e43e56bcb0fcfedc5a7bb5 Mon Sep 17 00:00:00 2001 From: Mike Norgate Date: Wed, 6 Dec 2023 09:49:03 +0200 Subject: [PATCH] run codegen --- docs/resources/rebalancing_schedule.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/resources/rebalancing_schedule.md b/docs/resources/rebalancing_schedule.md index bc65931a..cae485cb 100644 --- a/docs/resources/rebalancing_schedule.md +++ b/docs/resources/rebalancing_schedule.md @@ -97,17 +97,17 @@ Required: The `cron` expression can optionally include the `CRON_TZ` variable at the beginning to specify the timezone in which the schedule should be interpreted. - Example: - ```plaintext - CRON_TZ=America/New_York 0 12 * * ? - ``` - In the example above, the `CRON_TZ` variable is set to "America/New_York," indicating that the cron expression should be interpreted in the Eastern Time (ET) timezone. + Example: + ```plaintext + CRON_TZ=America/New_York 0 12 * * ? + ``` + In the example above, the `CRON_TZ` variable is set to "America/New_York" indicating that the cron expression should be interpreted in the Eastern Time (ET) timezone. To retrieve a list of available timezone values, you can use the following API endpoint: GET https://api.cast.ai/v1/time-zones - When using the `CRON_TZ` variable, ensure that the specified timezone is valid and supported by checking the list of available timezones from the API endpoint. + When using the `CRON_TZ` variable, ensure that the specified timezone is valid and supported by checking the list of available timezones from the API endpoint. If the `CRON_TZ` variable is not specified, the cron expression will be interpreted in the UTC timezone.