> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runchat.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Scheduling Tasks
> Set a Runchat workflow to re-run on a fixed schedule for polling, daily content generation, weekly summaries, and more
By default, Runchats only run when you trigger them in the Editor or App view. You can also set a workflow to re-run on a fixed interval, useful for polling data sources, generating recurring content, or sending alerts.
## Scheduling a workflow
Right-click any workflow tile (on the [Runchat Dashboard](https://runchat.com/dashboard) or in the editor's Workflows sidebar panel) and pick an interval from the **Schedule** section: **Hourly**, **Daily**, **Weekly**, or **Monthly**. The workflow will re-run automatically at that cadence.
## Removing a schedule
Right-click the workflow again and click **Remove Schedule**.
## Viewing scheduled tasks
Browse all your scheduled tasks at the [Tasks dashboard](/concepts/dashboard/tasks), where you'll find a calendar of upcoming runs, a run history for each scheduled job, and controls to change intervals or run a job on demand.
## Task inputs
Scheduled tasks always run with the input values currently set on the workflow. You can't pass different inputs to different runs of the same task. If you need to run a workflow on a schedule with varying inputs, use the [Runchat API](/api-reference) instead.
Because of this constraint, scheduled tasks are most useful when the workflow itself fetches fresh data when it runs. Common patterns:
* Check a spreadsheet or database for new content
* Check social media posts
* Check forums, message boards, or marketplaces
* Call external APIs (stock indexes, weather, etc.)
## Task outputs
Any workflow can be scheduled, but you won't see the result the way you do in the editor or app view. Schedule workflows that **act on the world outside Runchat** rather than ones that produce a result you'd want to inspect. For example:
* Write to a spreadsheet each week
* Send an email or newsletter each month
* Check an API endpoint every hour and send an alert if a condition is met
Scheduled runs consume credits or API tokens on every iteration. A workflow with large prompts running hourly can rack up costs fast, especially if it doesn't actually need to run that often.
## Next steps
* [Webhooks](/concepts/automations/webhooks): trigger workflows from external events instead of on a fixed schedule
* [Tasks dashboard](https://runchat.com/dashboard/tasks): view and manage your scheduled tasks
* [Runchat API](/api-reference): trigger workflows programmatically with custom inputs