Inspect a job or task

Replace the placeholders with values from your own authorized scope before copying this prompt into an MCP client.

Inputs

• {{workspace_id}} Stable workspace ID.
• {{application_id}} Stable application ID.
• {{record_id}} Exact job or task ID.
• {{record_kind}} Job or task, as identified in the original response.
• {{event_limit}} Maximum lifecycle events per page.
• {{character_limit}} Maximum characters per native log page.

Prompt

In {{workspace_id}} / {{application_id}}, inspect {{record_kind}} {{record_id}}.
Use read_v2_job with job_id for a job, or read_v2_task with task_id for a task. If starting with a job, find its task with list_v2_tasks and match sourceFamily Job and sourceId to the job ID. Page with nextSequence as after_sequence as needed.
For task diagnostics use read_v2_task_logs with event_limit {{event_limit}} and character_limit {{character_limit}}. Use lifecycle.nextEvent as after_event while lifecycle.hasMore is true and the page budget allows.
Return the job status and receipt_revision if present. For the task, report status and the latest visible lifecycle receiptRevision or errorCode. Include any pending or failed steps shown by the records.
Stop on scope or access failure. End after the reads.

Example inputs

Use the jobId from the disposable numeric write as the original caller. The job reports published and the task reports Succeeded. The final lifecycle event has the same receipt revision as the job. Use these small limits to see the lifecycle pagination. This job reports its diagnostics under lifecycle and returns null for sourceLog.

{"event_limit":1,"character_limit":1024}

Tools used include read_v2_job, list_v2_tasks, read_v2_task, and read_v2_task_logs. See the module guidelines and tool index.