QUA-1806: Note that deactivating a schedule keeps its cron expression

docs/flows/trigger-node.md

@@ -36,6 +36,11 @@ The Schedule trigger runs a flow automatically at a defined time interval. Use t
 !!! info "Timezone-aware scheduling"
     Schedules can run in any IANA timezone (for example, `America/New_York`, `Europe/Paris`, `Asia/Tokyo`), and Daylight Saving Time transitions are handled automatically. **UTC is the default** for new and existing schedules. The configured timezone is shown on the schedule card as an abbreviation, such as `Schedule (UTC)` by default or `Schedule (EST)` after selecting another timezone.
 
+!!! info "Deactivating a schedule keeps its cron expression"
+    When you deactivate a schedule, its cron expression is kept. Reactivating it later resumes the same schedule without setting it up again.
+
+    If a schedule was deactivated before May 7, 2026 and doesn't run after you reactivate it, re-enter its cron expression once to restore it. Schedules deactivated on or after that date keep working normally.
+
 ![schedule](../assets/flows/trigger-node/schedule.png)
 
 **Schedule Configuration**

docs/operations/export-operation/export-operation.md

@@ -46,6 +46,11 @@ After clicking **Export**, a confirmation message appears stating **"Export in m
 !!! info "Timezone-aware scheduling"
     Schedules can run in any IANA timezone (for example, `America/New_York`, `Europe/Paris`, `Asia/Tokyo`), and Daylight Saving Time transitions are handled automatically. **UTC is the default** for new and existing schedules. The configured timezone is shown on the schedule card as an abbreviation, such as `Schedule (UTC)` by default or `Schedule (EST)` after selecting another timezone.
 
+!!! info "Deactivating a schedule keeps its cron expression"
+    When you deactivate a schedule, its cron expression is kept. Reactivating it later resumes the same schedule without setting it up again.
+
+    If a schedule was deactivated before May 7, 2026 and doesn't run after you reactivate it, re-enter its cron expression once to restore it. Schedules deactivated on or after that date keep working normally.
+
 **Step 1:** Click **Schedule** to configure scheduling options for the Export Operation.
 
 ![schedule](../../assets/operations/export-operation/schedule-1.png)

docs/operations/materialize-operation/materialize-operation.md

@@ -85,6 +85,11 @@ After clicking **Run Now**, a confirmation message appears stating **"Operation
 !!! info "Timezone-aware scheduling"
     Schedules can run in any IANA timezone (for example, `America/New_York`, `Europe/Paris`, `Asia/Tokyo`), and Daylight Saving Time transitions are handled automatically. **UTC is the default** for new and existing schedules. The configured timezone is shown on the schedule card as an abbreviation, such as `Schedule (UTC)` by default or `Schedule (EST)` after selecting another timezone.
 
+!!! info "Deactivating a schedule keeps its cron expression"
+    When you deactivate a schedule, its cron expression is kept. Reactivating it later resumes the same schedule without setting it up again.
+
+    If a schedule was deactivated before May 7, 2026 and doesn't run after you reactivate it, re-enter its cron expression once to restore it. Schedules deactivated on or after that date keep working normally.
+
 **Step 1:** Click **Schedule** to configure scheduling options for the Materialize Operation.
 
 ![schedule](../../assets/operations/materialize-operation/schedule.png)

docs/operations/profile/profile.md

@@ -287,6 +287,11 @@ Click on the **Run Now** button, and perform the profile operation immediately.
 !!! info "Timezone-aware scheduling"
     Schedules can run in any IANA timezone (for example, `America/New_York`, `Europe/Paris`, `Asia/Tokyo`), and Daylight Saving Time transitions are handled automatically. **UTC is the default** for new and existing schedules. The configured timezone is shown on the schedule card as an abbreviation, such as `Schedule (UTC)` by default or `Schedule (EST)` after selecting another timezone.
 
+!!! info "Deactivating a schedule keeps its cron expression"
+    When you deactivate a schedule, its cron expression is kept. Reactivating it later resumes the same schedule without setting it up again.
+
+    If a schedule was deactivated before May 7, 2026 and doesn't run after you reactivate it, re-enter its cron expression once to restore it. Schedules deactivated on or after that date keep working normally.
+
 **Step 1**: Click on the **Schedule** button to configure the available schedule options in the profile operation.
 
 ![Schedule button to configure profile operation scheduling](../../assets/operations/profile/step-20-schedule-button.png)

docs/operations/scan/scan.md

@@ -174,6 +174,11 @@ Click on the **Run Now** button to perform the scan operation immediately.
 !!! info "Timezone-aware scheduling"
     Schedules can run in any IANA timezone (for example, `America/New_York`, `Europe/Paris`, `Asia/Tokyo`), and Daylight Saving Time transitions are handled automatically. **UTC is the default** for new and existing schedules. The configured timezone is shown on the schedule card as an abbreviation, such as `Schedule (UTC)` by default or `Schedule (EST)` after selecting another timezone.
 
+!!! info "Deactivating a schedule keeps its cron expression"
+    When you deactivate a schedule, its cron expression is kept. Reactivating it later resumes the same schedule without setting it up again.
+
+    If a schedule was deactivated before May 7, 2026 and doesn't run after you reactivate it, re-enter its cron expression once to restore it. Schedules deactivated on or after that date keep working normally.
+
 **Step 1:** Click on the **Schedule** button to configure the available schedule options for your scan operation.
 
 ![click-schedule](../../assets/operations/scan/step-20-click-schedule.png)

docs/operations/sync/sync.md

@@ -130,6 +130,11 @@ After clicking **Run Now**, a confirmation message appears stating **"Operation
 !!! info "Timezone-aware scheduling"
     Schedules can run in any IANA timezone (for example, `America/New_York`, `Europe/Paris`, `Asia/Tokyo`), and Daylight Saving Time transitions are handled automatically. **UTC is the default** for new and existing schedules. The configured timezone is shown on the schedule card as an abbreviation, such as `Schedule (UTC)` by default or `Schedule (EST)` after selecting another timezone.
 
+!!! info "Deactivating a schedule keeps its cron expression"
+    When you deactivate a schedule, its cron expression is kept. Reactivating it later resumes the same schedule without setting it up again.
+
+    If a schedule was deactivated before May 7, 2026 and doesn't run after you reactivate it, re-enter its cron expression once to restore it. Schedules deactivated on or after that date keep working normally.
+
 **Step 1:** Click on the **"Schedule"** button to configure the available schedule options in the sync operation.
 
 ![schedule-button](../../assets/operations/sync/step-10-schedule-button.png)