## TL;DR
Report only states you read from the server: the agent claimed a ClearML task was completed while it was still queued, so fetch the task status at report time, quote the exact state, and never infer completion from elapsed time or from a submission success. Queued looks like done to an agent that submitted the task and moved on. The only evidence of completion is a status read showing a terminal state with results attached.

```text
agent hallucinating ClearML task status as completed while task still queued error
```

## Use this when
- The check or run fails with this symptom: an agent hallucinates ClearML task status as completed while the task is still queued.
- You are working on an agent workflow submitting ClearML tasks and reporting their outcomes and the failure repeats on the same data or configuration.
- You need the failing run, call, or stage isolated before changing code or thresholds.

## Not for this skill when
- A task that completed and then was archived, where the status read needs the archive view to find it.
- The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

## Steps
1. Fetch the named task status now. Verify: the server reports it as queued with no results
2. Correct the report the agent issued, citing the live status. Verify: the correction names the actual state
3. Change the reporting step to poll the task until a terminal state before summarising. Verify: summaries are built only on terminal reads
4. Require result artifacts to exist before a completed claim. Verify: a completion claim links to present artifacts
5. Log the status read timestamp with every status statement. Verify: readers can judge the freshness of the claim

## Variant phrasings
### agent hallucinating ClearML task status completed queued
The shorter phrasing focused on the named failure.
### clearml task queued reported completed error
The symptom phrasing a searcher tries next.
### verify clearml task status before report fix
The variant naming the failing stage or tool directly.

Compatibility: ClearML task states and agent reporting workflows

## Why it happens
Agents summarise from intention: the plan said the task would run, the submission succeeded, so the summary says completed. Without a grounding read at report time, queue delays, failed tasks, and stuck tasks are all reported as successes, and the error is discovered by whoever acts on the report.

## Edge cases / pitfalls
- Submission success and execution success are different events; name them differently in reports.
- A poll loop needs a deadline and an honest still-queued outcome, or the grounding fix becomes a hang.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_sS6dLZylMPAEra0SIs9x4Q