Tasks
Tasks are content items that run to completion. Unlike apps, which stay running to serve requests, a task executes once and then stops — for example an R script that generates a report, a Python ETL pipeline, or a Quarto document that renders to HTML.
See the content items overview for the full list of supported task types.
Task types
Section titled “Task types”| Content Type | Description |
| ------------ | ----------- |
| r | An R script with the extension .R or .r. |
| rmd | An R Markdown document. Can be served as a static site. |
| quarto-r | A Quarto document using an R runtime. Can be served as a static site. |
Python
Section titled “Python”| Content Type | Description |
| ------------ | ----------- |
| python | A Python script with the extension .py. |
| quarto-py | A Quarto document using a Python runtime. Can be served as a static site. |
| Content Type | Description |
| ------------ | ----------- |
| julia | A Julia script. |
| quarto-jl | A Quarto document using a Julia runtime. Can be served as a static site. |
Working with tasks
Section titled “Working with tasks”- Invoking tasks — run tasks on-demand via the UI, CLI, or REST API
- Scheduling tasks — run tasks on a recurring schedule
- Static sites — serve static HTML generated by tasks like R Markdown or Quarto
Deployment
Section titled “Deployment”See the deployment guide for how to deploy tasks using the CLI or via git integration, and the language-specific guides for project requirements: