获取任务执行

API 参考

获取任务执行

Request

返回单条 RPA 执行记录的详情。

前置条件：执行记录必须属于你的团队。若执行记录、其所属计划或其云手机已不存在，调用失败。
副作用：无。只读。可带退避安全重试。
状态取值：与 /cloudphone/rpa/subTask/page 同一套刻度。
说明：即使代理此后已被删除，也会解析出代理详情，因此历史执行仍能看到它当时用的是什么。

Security

Authorization

Path

idintegerrequired

执行任务 ID

Example:1678919049331331

Bodyapplication/jsonrequired

taskIdstring or null

任务 ID

taskNamestring or null, [ 1 .. 255 ] characters

任务名称

taskStateinteger or null, [ 0 .. 9 ]

计划状态；0：等待执行；1：执行中；2：执行完成；3：取消

templateIdstring or null, [ 0 .. 99999999999 ]

模板 ID

templateTitlestring or null, [ 0 .. 255 ] characters

模板标题

cloudPhoneIdstring or null

云端手机ID

Example:"1559133625483282"

cloudPhoneNamestring or null, [ 0 .. 100 ] characters

云手机名称

beginTimestring or null

任务开始时间 UTC+0 时区

Example:"2025-01-01 23:59:59"

endTimestring or null

任务结束时间（UTC+0 时区）

Example:"2025-01-02 23:59:59"

pageNointeger or null

默认值：1

Example:1

pageSizeinteger or null

默认值：10

curl -i -X POST \
  https://api.morelogin.com/cloudphone/rpa/subTask/detail/1678919049331331 \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "taskId": null,
    "taskName": null,
    "taskState": null
  }'

Responses

成功。data 是对象，包含字段 id、taskName、taskState、cloudPhoneId、cloudPhoneName、templateName、…。

Headers

any

Bodyapplication/json

codeintegerrequired

响应代码，0 表示成功，大于 0 表示失败

msgstring or nullrequired

错误信息

requestIdstringrequired

请求跟踪 ID

dataobjectrequired

Response

{
  "code": 0,
  "msg": null,
  "requestId": "0d8b6f1c-9f4e-4d02-9d1a-7c3f5a1b2c3d",
  "data": {
    "id": "1673823102599682",
    "taskName": "example-name",
    "taskState": 1,
    "cloudPhoneId": "1673823102599682",
    "cloudPhoneName": "example-name",
    "templateName": "example-name",
    "handleFailCode": "string",
    "handleFailReason": "string",
    "handleResult": 1,
    "handleResultAttachment": "string",
    "handleTime": "2026-09-01 12:00:00",
    "endTime": "2026-09-01 12:00:00",
    "powerOnTime": "2026-09-01 12:00:00",
    "triggerNextTime": "2026-09-01 12:00:00",
    "triggerTime": "2026-09-01 12:00:00",
    "createDate": "2026-09-01 12:00:00",
    "createMember": "string",
    "updateDate": "2026-09-01 12:00:00",
    "updateMember": "2026-09-01 12:00:00"
  }
}