{"version":"2.1.248","anchor":"context-remote-failures-can-hide-the-raw-error","canonical_anchor":"context-remote-failures-can-hide-the-raw-error","heading":"\/context remote failures can hide the raw error","tier":"soon","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/context-remote-failures-can-hide-the-raw-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### \/context remote failures can hide the raw error\n\nRemote \/context failures can hide the underlying error and just say it couldn't fetch.\n\n**What**\n\nWhen the remote context fetch fails and the same unnamed per-session condition holds, you see only \"Couldn't fetch context from remote\" and the underlying error goes to the log at error level; otherwise the error text is still shown inline.\n\n**Evidence**\n\n`Couldn't fetch context from remote`\n\n- Area: Elsewhere\n- Names: `\/context`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}