Make task polling behavior and reasoning more explicit

Co-authored-by: Connor Peet <[email protected]>

Author: LucaButBoring

docs/specification/draft/basic/utilities/tasks.mdx

@@ -223,7 +223,7 @@ After a task completes the operation result is retrieved via [`tasks/result`](/s
 
 To retrieve the result of a completed task, requestors can send a `tasks/result` request:
 
-While `tasks/result` blocks until the task reaches a terminal status, requestors can continue polling via `tasks/get` in parallel if they are not actively blocked waiting for the result. This allows requestors to monitor status changes or display progress updates while the task executes, even after invoking `tasks/result`.
+While `tasks/result` blocks until the task reaches a terminal status, requestors can continue polling via `tasks/get` in parallel if they are not actively blocked waiting for the result, such as if their previous `tasks/result` request failed or was cancelled. This allows requestors to monitor status changes or display progress updates while the task executes, even after invoking `tasks/result`.
 
 **Request:**