Agent Application DevelopmentAccount
Knowledge catalogChoose core direction and segmented content
Practice 14AdvancedImplementationAbout 18 minutes

Corresponding knowledge: Delivery conditions and shared deadlines for parallel results

Three tools are called in parallel. One is very slow and the other fails. How to return the result?

Examine asynchronous concurrency, deadlines, cancellation propagation, and partial results.

Learn corresponding knowledgeInterview questions · Answer independently →
asyncioConcurrencyDeadline

Knowledge content check2026-10-03 · Check the source of the original question2026-10-02

The knowledge corresponding to this exercise:

Delivery conditions and shared deadlines for parallel results · Principle explanation →
Knowledge unit directory

LEARN · PRACTICE · REFLECT

Knowledge exercises·Independent answers

My notes and review ↗

Principles and Solutions have been collapsed. Explain the core mechanism, boundaries and verification methods in your own words, and then compare them.

Answers and personal notes

Each modified commit will be kept as an independent history. Your level of mastery is up to you to evaluate yourself against the standards.

Explain in your own words first

The core principles, analysis, Q&A and migration cases have been closed. When you are ready, unfold it and compare it with the content to find any omissions.

Hands-on verificationComplete on demand · Suggestions15 minutes

Write pseudocode to call three read-only tools in parallel and return item-by-item status at the 500ms deadline.

Expand acceptance requirements and checkpoints
  • The slowest task does not hang indefinitely
  • Success and failure are visible separately
  • When all must be successful, partial completion cannot be pretended to be completed.

Key inspections

  • Design concurrency by dependencies and necessity
  • Share deadline instead of resetting timeout
  • Handling differences between local cancellation and remote actions