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

[RafaelOsiro]

Overview

Documents that deactivating a schedule keeps its cron expression, so reactivating later resumes the same schedule without setting it up again. Adds a one-time note for schedules deactivated before May 7, 2026 that may need their cron re-entered once.

Key Changes

• Schedule deactivation behavior: Added an info admonition to all six pages that document scheduling, explaining that the cron expression is kept through deactivation and reactivation resumes the same schedule.
• One-time recovery note: Same admonition includes a corrective step for users whose schedules were deactivated before May 7, 2026: re-enter the cron once if the schedule doesn't run after reactivation.

Pages to Test

• http://localhost:8000/flows/trigger-node/ — Schedule trigger section
• http://localhost:8000/operations/export-operation/export-operation/ — Schedule section
• http://localhost:8000/operations/materialize-operation/materialize-operation/ — Schedule section
• http://localhost:8000/operations/profile/profile/ — Schedule section
• http://localhost:8000/operations/scan/scan/ — Schedule section
• http://localhost:8000/operations/sync/sync/ — Schedule section

[greptile-apps]

Greptile Summary

This PR adds an identical !!! info admonition to all six scheduling-related documentation pages, explaining that deactivating a schedule preserves its cron expression and that reactivation resumes the same schedule automatically. It also includes a one-time recovery note for schedules deactivated before May 7, 2026.

• Six pages updated (trigger-node, export-operation, materialize-operation, profile, scan, sync) with identical wording, placed consistently after the existing "Timezone-aware scheduling" admonition.
• Backward-compatibility note targets schedules deactivated before May 7, 2026 and instructs users to re-enter their cron expression once if the schedule doesn't resume automatically after reactivation.

Confidence Score: 5/5

Documentation-only change; no code is modified and there is no risk of runtime regression.

All six admonition blocks are worded identically, placed consistently after the existing timezone note, and the May 7, 2026 cutoff date is already in the past, making the backward-compatibility guidance immediately actionable for affected users.

No files require special attention.

Important Files Changed

Filename	Overview
docs/flows/trigger-node.md	Adds deactivation/reactivation admonition after existing timezone info block; content is consistent with the other five pages.
docs/operations/export-operation/export-operation.md	Adds identical schedule-deactivation admonition; placement and wording match all other changed pages.
docs/operations/materialize-operation/materialize-operation.md	Adds identical schedule-deactivation admonition; no issues found.
docs/operations/profile/profile.md	Adds identical schedule-deactivation admonition; no issues found.
docs/operations/scan/scan.md	Adds identical schedule-deactivation admonition; no issues found.
docs/operations/sync/sync.md	Adds identical schedule-deactivation admonition; no issues found.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([Schedule active]) -->|User deactivates| B[Schedule deactivated\ncron expression retained]
    B -->|Deactivated on or after May 7 2026| C[Reactivate]
    B -->|Deactivated before May 7 2026| D[Reactivate]
    C --> E{Schedule runs?}
    E -->|Yes| F([Running normally])
    D --> G{Schedule runs?}
    G -->|Yes| F
    G -->|No| H[Re-enter cron expression once]
    H --> F

Loading

_{Reviews (1): Last reviewed commit: "docs(schedules): note that deactivating ..." | Re-trigger Greptile}