Scheduling & Automation
Create Schedule
POST
Creates or updates an auto-update schedule for a specific container. SetDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/Finsys/dockhand/llms.txt
Use this file to discover all available pages before exploring further.
enabled: false to delete the schedule.
Path Parameters
Name of the container to schedule (URL-encoded if contains special characters)
Query Parameters
Environment ID. If not provided, schedule applies to the default environment.
Request Body
Enable or disable the schedule. Setting to
false will delete the schedule entirely.Schedule frequency type:
daily- Runs once per dayweekly- Runs once per weekcustom- Custom cron expression
cronExpression if not provided.Cron expression defining when the schedule runs. Standard 5-field format:
minute hour day month weekdaySee Cron Expression Format for details and examples.Criteria for blocking updates based on vulnerability scan results:
never(default) - Never block updates based on vulnerabilitiesany- Block update if any vulnerabilities are foundcritical_high- Block only if critical or high severity vulnerabilities foundcritical- Block only if critical severity vulnerabilities foundmore_than_current- Block if new image has more vulnerabilities than current
Cron Expression Format
Cron expressions use standard 5-field format:Field Values
- minute: 0-59
- hour: 0-23 (24-hour format)
- day: 1-31 (day of month)
- month: 1-12
- weekday: 0-7 (0 and 7 are Sunday, 1 is Monday)
Special Characters
*- Any value (e.g.,*in hour field means every hour)*/n- Every nth value (e.g.,*/6in hour field means every 6 hours)n-m- Range (e.g.,1-5in weekday field means Monday through Friday)n,m- List (e.g.,1,15in day field means 1st and 15th of month)
Common Schedule Examples
Response
Returns the created or updated schedule configuration.Unique schedule identifier
Name of the container
Associated environment ID
Whether the schedule is enabled
Schedule frequency type (daily, weekly, or custom)
The cron expression for this schedule
The vulnerability blocking criteria
Only present when
enabled: false is sent, indicating the schedule was deletedRequest Examples
Response Examples
Notes
- Setting
enabled: falseperforms a hard delete of the schedule - The schedule is automatically registered with the task scheduler when enabled
- Vulnerability criteria only applies when environment has scanning enabled
- Schedules respect the environment’s configured timezone
- Updates will be skipped if the container is part of a running stack
