errors.events.latest

Read an issue’s latest event in full

GET /errors/api/issues/{issueId}/events/latestIAM errors:GetEventsRead

Request syntax

GET /errors/api/issues/{issueId}/events/latest

Path parameters

  • issueIdRequired

    string

    Constraints: 1-80 chars, /^(\d+|[A-Za-z0-9][A-Za-z0-9-]*-[0-9A-Za-z]+)$/

Response

200 with { row, event, attachments }: `row` the event’s fields as `list` gives them, `event` the event as the SDK sent it (exception and stack trace, breadcrumbs, request, contexts, …), `attachments` its files (id, filename, contentType, size). 404 when the issue does not exist or has no event left, 403 without errors:GetEvents on its project.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow errors:GetEvents on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud errors events latest issueId

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_errors_events_latest.