Start a Workload Cron Run
start_workload_cronTrigger an immediate run of a cron workload (useful when the schedule is suspended or you need an out-of-band execution). Each call starts another run with real side effects; confirm with the user.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"gvc": "<gvc>",
"name": "<name>",
"location": "<location>"
},
"name": "start_workload_cron"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| gvc | Yes | GVC name. | |
| org | No | Organization slug. | |
| name | Yes | Workload name. Immutable: renaming is delete and recreate, which loses the URL and internal DNS. | |
| location | Yes | Location where this job should execute. Must be one of the locations where this workload is deployed — call list_deployments to list the workload's locations. | |
| containerOverrides | No | Omit to run the job as configured. Changes for this run only, one entry per existing container by name (get_resource kind "workload" lists them); fields left out keep the stored values. Shape: [{name, image, command, args: [], env: [{name, value}], cpu, memory}]. env values are literals or cpln://secret/NAME.KEY, never a password or key. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| data | No | The full result. Read this, not only the summary. | |
| details | No | ||
| summary | Yes | ||
| nextSteps | No |