## TL;DR
Page the listing and checkpoint progress: listing ClearML tasks across 20 projects in one call times out, so query per project with pagination, persist the results per project, and let the agent resume from the last finished project. Twenty projects of task history is a reporting job, not a lookup. A single synchronous sweep gives the agent one giant failure instead of twenty small successes.

```text
agent timed out when agent tried to list ClearML tasks across 20 projects error timeout failure
```

## Use this when
- The check or run fails with this symptom: an agent times out listing ClearML tasks across 20 projects.
- You are working on an agent workflow auditing or cleaning up ClearML tasks across many projects 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 single project listing that still times out, which points at the ClearML server rather than the sweep design.
- The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

## Steps
1. Split the listing by project and time one project query. Verify: a single project returns inside the limit and sizes the job
2. Page each project with a page size the server answers quickly. Verify: pages return without timeouts
3. Persist results after each project with the project id as the checkpoint. Verify: a timeout now costs one project, not the sweep
4. Run the full sweep with resume from the checkpoint. Verify: all twenty projects are listed
5. Summarise from the stored pages instead of re-querying. Verify: the report builds without new API calls

## Variant phrasings
### agent timed out list ClearML tasks 20 projects timeout
The shorter phrasing focused on the named failure.
### clearml list tasks many projects agent error
The symptom phrasing a searcher tries next.
### clearml task listing pagination sweep fix
The variant naming the failing stage or tool directly.

Compatibility: ClearML tasks API pagination, agent sweep workflows

## Why it happens
Agents default to one broad query because it is the shortest code. Task listings grow with every run a team has ever launched, and multi-project scopes multiply that by the project count, so the response assembly itself exceeds the agent or API timeout.

## Edge cases / pitfalls
- Archived and completed tasks dominate old projects; filter by status early when the audit only needs active tasks.
- Cache the sweep with a timestamp; task audits rarely need second level freshness.

## Provenance

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