Run scheduled application tasks

Scheduled tasks let Coolify run a command inside an application container on a recurring schedule. Use them for framework schedulers, queue maintenance, cleanup commands, imports, and other work that belongs inside the deployed application.

Coolify runs the command in a shell inside a running container. The schedule uses the timezone configured for the application's deployment server.

Detailed scheduled-task reference

This page covers the application workflow. The Scheduled Tasks section in Core explains task management, execution history, output downloads, cron behavior, and troubleshooting in more detail.

Open Scheduled Tasks

Open the application page

Open the application and select Configuration > Scheduled Tasks.

Choose the detailed guide

Select + Add to start a task, or select an existing task to manage it. Follow the Core guide for the complete field-by-field procedure.

Run the first execution

Open the task and select Execute Now while the application is running.

Open the new record under Recent executions. Confirm that it finishes successfully and that its output or effect matches what the command should produce.

Application-specific behavior

When the schedule is due, Coolify finds the application's running container and runs the saved command through sh.

Before following the detailed guide, check these application-specific requirements:

Test commands that change or delete data through the application Terminal first.
Enter the command as it should run inside the container; do not include docker exec.
Set Container name when the application has more than one container.
The schedule uses the timezone configured for the application's deployment server.
Timeout (seconds) accepts 60 to 36000 and defaults to 300.

An execution fails when no application container is running, the configured container cannot be found, the command exits with an error, or the command exceeds its timeout.

Coolify records the status, timing, and captured output under Recent executions. A successful exit does not prove that the command produced the intended application result, so verify the affected records, files, or external system when necessary.

Use the detailed Core guides

Create a task

Review every field, accepted value, and creation step.

Manage tasks

Update, enable, disable, run, or delete a task.

Review execution history

Inspect statuses, timing, command output, and logs.