5.2 KiB
title, type, status, created, updated, verified_on, review_after, confidence, tags, sources
| title | type | status | created | updated | verified_on | review_after | confidence | tags | sources | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Asana Is Unreachable From CT460 on Both Paths — MCP Server Never Authenticated, Hosted Connector Rejects the Call Shape | incident | active | 2026-11-01 | 2026-11-01 | 2026-11-01 | 2026-11-08 | high |
|
|
Asana Is Unreachable From CT460 on Both Paths — MCP Server Never Authenticated, Hosted Connector Rejects the Call Shape
Headline
The estate has two independent Asana integrations on CT460, and neither can complete a read — which went unnoticed until an interactive session spent 2026-10-31 evening retrying both to answer a single question ("where does Remembrance Day stand?").
| Path | Surface | Live state 2026-10-31/11-01 |
|---|---|---|
MCP server asana |
https://mcp.asana.com/v2/mcp, auth: oauth, enabled: true (hermes mcp list → ✓ enabled) |
Never authenticated. Every attempt logs MCP OAuth setup failed for 'asana': … non-interactive environment and no cached tokens found. Run \hermes mcp login asana` interactively first to complete initial authorization.` |
| Hosted connector | connectors__asana__GET_A_TASK, …__SEARCH_TASKS_IN_WORKSPACE |
Reaches Asana but returns 422 INVALID_ARGUMENTS — "Input should be a valid list on parameter `opt_fields`". 12+ identical retries in one session. |
Evidence
MCP server — no token, ever. ~/.hermes/mcp-tokens/ holds exactly one file:
-rw------- 1 hermes hermes 319 Oct 26 01:07 asana.client.json
A registered client with no token file → the OAuth flow was started (client registered
2026-10-26 01:07) and never completed. config.yaml → mcp_servers.asana reads
{auth: oauth, enabled: true, url: https://mcp.asana.com/v2/mcp}. The earliest Asana trace in retained
logs is an HTTP 401 from mcp.asana.com/v2/mcp at 2026-10-27 16:35:05, followed immediately by
OAuth discovery calls.
Failure volume (log lines across logs/agent.log* + logs/errors.log*; the failure is written to
both files, so line counts roughly double the number of events):
| Day | MCP OAuth setup failed for 'asana' lines |
|---|---|
| 2026-10-21 | 455 |
| 2026-10-22 | 469 |
| 2026-10-23 | 576 |
| 2026-10-24 | 576 |
| 2026-10-25 | 576 |
| 2026-10-26 | 301 |
| 2026-10-27 | 439 |
| 2026-10-28 | 1 150 |
| 2026-10-29 | 1 154 |
| 2026-10-30 | 862 |
| 2026-10-31 | 1 156 |
| 2026-11-01 (to 00:16) | 14 |
| Total retained | 7 728 |
The earliest retained line is 2026-10-21 05:09:43 (errors.log.2) — the gap predates the retained
log window; this is a chronic condition, not a 10-31 regression. The 10-31 peak coincides with the
evening Pulse session hammering the path.
Hosted connector — the call, not the credential. From 20261031_210329_b35440 (the Conduit Pulse
"Remembrance Day" session), repeated at 22:17:47, 22:20:42, 22:26:31, 22:31:25, 22:36:45, 23:14:45,
23:26:46, 23:28:55, 23:30:34, 23:39:31, 23:41:48, 23:51:19 — each call burning 11–20 s:
tools.managed_gateway_identity: connector connectors.execute 422 INVALID_ARGUMENTS
Tool tool_call returned error: {"results":[{"name":"connectors__asana__GET_A_TASK","error":
{"code":"INVALID_ARGUMENTS","message":"Invalid request data provided\n- Input should be a valid list
on parameter `opt_fields`…"}}]}
The connector is authorised (it is the MCP path that cannot authenticate), so the block is purely
argument shape: opt_fields must be a JSON list, and a string/comma-form is rejected.
Impact
- Non-interactive sessions (cron, background jobs, Conduit background investigations) cannot read Asana at all — the MCP path needs an interactive browser login that cron cannot provide.
- Interactive sessions get the hosted connector, but the agent re-issued the same mis-shaped call a dozen times instead of adapting — ~3 minutes of model time spent failing identically.
- Asana-backed user requests (task status behind the Conduit Pulse flow) degrade to guesses.
Remediation (not performed — this audit records, it does not re-authorise)
- Run
hermes mcp login asanafrom an interactive session to complete the OAuth flow; confirm~/.hermes/mcp-tokens/asana.json(or equivalent token file) appears afterwards, then re-probe the MCP server. - Or disable the
asanaMCP server if the hosted connector is the intended path — two Asana paths on one host is itself the source of the confusion, and one of them has never worked. - For the connector: pass
opt_fieldsas a JSON list, not a comma-separated string. - Watch for the silent-cost pattern: a path that fails every time still burns a tool call each time. 1 100+ failures/day means the failure is being retried, not fixed.
Related
- systems/hermes-agent — MCP server inventory and auth state
- systems/conduit — the Pulse flow that needed the Asana task status
- systems/scheduled-tasks — cron fleet (the surface that cannot authenticate interactively)
- incidents/2026-08-08-gitea-config-backup-push-dead — the same "green row, dead destination" class