Read integration-backed results

For integration-backed tasks, you do not fetch the number; the app does. That is a convenience and a risk: it is easy to treat "the app will handle it" as "the result is settled." It is not. The baseline is fixed early, the window still has to close, and provider reads can fail. Reading integration-backed results correctly means knowing which state the result is in (pending, final, or failed and visible) and acting accordingly.

After marking an integration-backed task done with its binding saved (see Connect published URLs or provider identifiers where required), at any point until the window closes and after.

• The task is done and, where the card asks for one, bound to the exact published page or post.
• The relevant integration shows Connected (Workspace → Integrations).

1. 1Open the task and confirm it shows "Task completed. Measurement pending." This is the pending state: the app knows what to read and the window is running. Do nothing except wait.
2. 2Note what the result is measured against: the baseline the app captured when you marked the task done, or zero from the moment you saved a published URL. The final result is read as movement from that baseline. The app compares; you interpret.
3. 3While the window runs, the card may show "Live tracking" with the current value and the date it finalizes; that value is interim. When the window closes, the card shows "Final result" with the value, the target, the verdict, and when it was last updated.
4. 4If a provider read failed, it stays visible; the app does not silently drop the result. Read the failure state, then go to Workspace → Integrations, run Sync Now on the provider, and check whether the read recovers on retry.
5. 5If the window closes without a usable read, the card shows "Measurement ended without a usable result." Note what was attempted and why it failed in your review, and fix the binding or connection before the next task. A visible failure is evidence; a silently missing number is not.
6. 6Never treat a pending or interim reading as final. The verdict comes after the window closes (see Interpret met, partial, missed, and inconclusive results).

These states are all legitimate: pending ("Task completed. Measurement pending.", with the date the final result is due), interim ("Live tracking", with the date it finalizes), final ("Final result", with the value, target, and verdict), and failed but visible ("Measurement temporarily unavailable." while the app retries the provider read, or "Measurement ended without a usable result." if the window closed without one). What you should never see is a number presented as final before the window closes.