Hex scheduled runs execute the published app, never the draft

When an agent sets up Hex automation, always publish the app first and verify the published version contains the intended cells: a scheduled run against an unpublished draft silently runs stale code. If you need the agent to answer fresh questions on a schedule, use Tasks, not scheduled app runs. Check the plan limits too: Professional allows only one scheduled run per project.

Context: Hex docs (scheduled runs): scheduled runs always execute the currently published version of the app, never the draft. You must publish before the schedule will pick up your changes. Maximum frequency is hourly, and scheduling is gated by plan (Professional is limited to one scheduled run per project). To schedule the Hex agent itself against a fresh prompt instead of re-running an app, use Tasks.

Source: Hex docs (scheduled runs): scheduled runs always execute the currently published version of the app, never the draft. You must publish before the schedule will pick up your changes. Maximum frequency is hourly, and scheduling is gated by plan (Professional is limited to one scheduled run per project). To schedule the Hex agent itself against a fresh prompt instead of re-running an app, use Tasks.

Verified resolution: When an agent sets up Hex automation, always publish the app first and verify the published version contains the intended cells: a scheduled run against an unpublished draft silently runs stale code. If you need the agent to answer fresh questions on a schedule, use Tasks, not scheduled app runs. Check the plan limits too: Professional allows only one scheduled run per project.

Source URL: https://learn.hex.tech/docs/share-insights/scheduled-runs-and-notifications