列出自动化运行历史
列出调用者可管理规则的运行历史。
调用限制
| 项 | 值 |
|---|---|
| 速率限制 | 1,000 次/分钟;50 次/秒 每账户 |
| 权限 | 有效 app_key;结果按调用者可见范围过滤 |
授权
App key issued from the Flashduty console. Required on every public API call. Keep it secret — it grants the same access as the owning account.
请求体
目标规则 ID。
页码,从 1 开始。
每页数量。
x <= 100运行状态过滤。
queued, running, retrying, succeeded, partial, failed, skipped, abandoned 触发来源过滤条件。
schedule, debug, manual, http_post, oncall_incident 开始时间下界,Unix 毫秒。
开始时间上界,Unix 毫秒。
响应
Success
Standard response envelope used by every Flashduty public API. On success data contains the endpoint-specific payload and error is absent. On failure error is present and data is absent. request_id is always present and is also mirrored in the Flashcat-Request-Id response header.
Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.
"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"
Error payload inside the response envelope. Present only on non-2xx responses.
Endpoint-specific payload. See each operation's 200 response schema.