Run history errors and environments¶
HTTP |
code |
Description |
|---|---|---|
400 |
2 |
Invalid workspace/path ID, state, or RFC3339 timestamp. |
403 |
5 |
Service-layer permission denial. |
503 |
15 |
Authentication/shared PDP or required service dependencies unavailable. |
500 |
1 |
Other internal read failure; this API returns the fixed message internal error. |
List success uses numeric code=0/data. Service errors use numeric code/message without data. Identity/runtime-credential rejections before the handler use their own envelopes; not every 401 has numeric code 6. A valid task history with no matching runs can return a 200 empty list; it does not guarantee a parent-task 404. Adjacent detail/event APIs may return 404 for missing runs; that is separate from list semantics.
Last updated on