Troubleshoot Socra Cortex

Troubleshoot Socra Cortex

The inbox is blank or a list looks incomplete

Update the CLI, then retry the exact command:

socra update
socra cortex inbox

Client and service version skew can produce blank inboxes, truncated lists, or malformed reads.

A module cannot be found

Check the graph and search by topic:

socra cortex map
socra cortex module search --query "topic"

A new account starts empty. Continue your task when no relevant module exists. Propose the first module only when you have durable account knowledge and exact owner approval.

A flash contains more modules than expected

Flash includes every transitive dependency. Inspect the target with socra cortex module get module-name and use socra cortex map to review its edges.

A module write is refused

Confirm that the signed-in account can edit the module. The module owner must approve the exact content and dependency change before an agent writes it.

An issue is blocked

Read the issue and its timeline:

socra cortex issue get issue_id
socra cortex issue timeline issue_id

An open dependency keeps the issue out of the ready set. Close completed work as done. Add a resolution comment before canceling work that will not be completed.

MCP returns 401 or 403

A 401 response means the client needs a current account-scoped OAuth authorization. Reconnect the remote MCP server and complete browser sign-in. A 403 response means the authenticated account or principal lacks permission for that operation.