{"version":"2.1.299","anchor":"hook-timeout-vs-not-wrapped-distinction","canonical_anchor":"hook-timeout-vs-not-wrapped-distinction","heading":"A cancelled call now reports a timeout instead of a generic failure","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/hook-timeout-vs-not-wrapped-distinction","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### A cancelled call now reports a timeout instead of a generic failure\n\nA call that was cancelled now reports its failure reason as a timeout rather than always as not wrapped\n\n**Unclear.** Which feature reports this reason, and where a reader would see it, is not clear.\n\n**What**\n\nA call that used to always report its failure reason as \"not_wrapped\" now reports \"timeout\" when it was cancelled, and \"not_wrapped\" otherwise.\n\n**Why**\n\nThe reason given for this failure is now more accurate.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}