Skip to documentation content

Support

Troubleshooting

Resolve common issues with captures, sources, notifications, and API access.

UpdatedMay 7, 2026

On this page

Common problems and what to check first.

Slack or Teams captures are not creating decisions

  • Confirm the provider is connected in Integrations.
  • Open the integration and check that a rule exists.
  • Check that the rule listens to the right channel, team, or source scope.
  • Check that the reaction matches the rule.
  • Confirm the app is allowed in the source channel.

GitHub is not creating decisions

  • Confirm the GitHub App is installed and not suspended.
  • Open Integrations > GitHub and check the rule.
  • Check the source repository or path on the rule.
  • Check the trigger label if the rule uses labels.
  • For pull request flows, confirm the PR event actually happened.

Jira is not creating decisions

  • Confirm Jira is connected.
  • Open Integrations > Jira and check the rule.
  • Check the Jira project key or source scope.
  • Check the trigger label or issue behavior expected by the rule.
  • Confirm the webhook is still installed in Jira.

I cannot find a decision

  • Search Decisions by title, owner, project, slug, or record ID.
  • Check the project if the decision was assigned.
  • Use command search from the header.
  • Open Chats, attach the likely project, and ask about the topic.

A risk looks wrong

  • Open the risk.
  • Review the target, evidence timeline, and recommendation.
  • Assign an owner if the risk needs follow-up.
  • Mark mitigated, snooze, mark not a risk, or reopen from the risk detail page.

A guideline is not checking a project

  • Open the project.
  • Go to Guidelines.
  • Confirm the guideline is assigned and active.
  • Check whether the guideline has at least one active check.

Notifications are not showing up

  • Check the header bell quick view.
  • Open Notifications and clear filters.
  • If Slack delivery is expected, confirm Slack is connected.
  • Check quiet hours or delivery rules if your workspace uses them.

API key or MCP access is not working

  • Confirm the key exists in Settings > Security & data > API keys.
  • Check the key scopes.
  • Send the key as a bearer token:
Authorization: Bearer YOUR_API_KEY
  • Use auth_whoami to verify MCP identity.

Chat is not responding

  • Confirm an AI provider is configured in Settings > Security & data > AI settings.
  • Attach a project, decision, or document for better grounding.
  • Check workspace plan and usage limits.

Document context is missing

  • Confirm the document exists and is linked to the right project or decision.
  • Check that text extraction is ready for the file.
  • For MCP-created documents, use get_document with extracted text enabled.

Something else

Use the in-app feedback form when a workflow is blocked or the source data looks wrong.