列出自动化运行历史
列出调用者可管理规则的运行历史。
限制说明
使用说明
- 仅当调用者可管理规则时才可查看运行历史:个人规则仅限创建者;团队规则限账户管理员或规则所属团队成员。
授权
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,取自 POST /safari/automation/rule/list 返回的列表。
页码,从 1 开始。
每页数量。
x <= 100运行状态过滤:queued 排队中、running 运行中、retrying 重试中、succeeded 成功、partial 部分成功、failed 失败、skipped 已跳过(如规则或触发器失效)、abandoned 已放弃(超过时效未完成被系统终结);省略则不过滤。
queued, running, retrying, succeeded, partial, failed, skipped, abandoned 触发来源过滤:schedule 定时调度、debug 调试运行、manual 手动触发、http_post HTTP POST 触发、oncall_incident On-call 故障触发;省略则不过滤。
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.