Lifecycle detail
Validate state and sequence.
The homepage sample begins with durable creation, pauses for an elicitation request, resumes working and completes with a tool result. Each line repeats complete task metadata so it can represent a tasks/get response or status notification snapshot.
Change IDs and timestamps, keep input request keys unique for the task lifetime, and validate the full trace before exercising real polling.
Continue debugging
- Run the lifecycle validator.
- Review status-specific payloads.
- Check 2025-to-2026 migration.
- Test storage, routing, permissions and polling with the official SDK used in production.
MCP Task Trace is independent and is not affiliated with the Model Context Protocol project.