Diagnose Task Run
diagnoseInvestigate one failed task run by reviewing its status, messages, parameters, upstream task statuses, newest log tail, and artifact filenames to pinpoint what went wrong.
Instructions
Deep dive on one failed task run: its status and messages, taskParameters and runParameters, the statuses of the upstream tasks it depends on, the tail of its newest log, and its artifact filenames. Over-long parameter values, the log tail and the artifact list are capped, and the response says which parts were cut. Use download_task_run_log or download_task_run_artifact when the tail is not enough.
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": {
"task_run_id": "<task_run_id>"
},
"name": "diagnose"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account_id | No | Act on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers. | |
| task_run_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||