Help

How to troubleshoot Currai

Fix missing events, failed skill setup, unmatched signals, event quota responses, and Slack delivery problems.

Start with the first point where the workflow differs from what you expected. Keep ingestion failures separate from the user-facing AI request while you investigate.

The application never connects

Check these in order:

Confirm the Currai helper runs on the server, not in browser code.
Confirm CURRAI_BASE_URL, CURRAI_PUBLIC_KEY, and CURRAI_SECRET_KEY exist in the process handling the real interaction.
Restart the local application or redeploy after changing environment values.
Run the real chat, agent, or MCP entrypoint rather than a standalone demo script.
Await capture before a serverless handler or short-lived process exits.
Inspect server logs for HTTP status codes, timeouts, and connection failures.

If the skill selected the wrong monorepo package, give the coding agent the exact package path and real AI entrypoint, then ask it to repeat verification.

Authentication fails

Status	Likely cause	Fix
`401 Unauthorized`	The key is missing, malformed, swapped, revoked, or belongs to a different workspace	Create a new ingestion key and update the server environment
`403 Forbidden`	The key does not have ingestion access	Use the ingestion key created by onboarding or Workspace Settings
`404 Not Found`	The authenticated workspace no longer exists	Create a key in the workspace you are currently viewing
`409 Conflict`	An event arrived before its session	Make the helper await session creation before sending the first event

Secrets are shown once. If the stored secret is lost, revoke the old key and generate a replacement.

Currai returns EventLimitExceeded

When a workspace has no remaining monthly events, ingestion returns HTTP 429 with the current usage, plan limit, and reset time. Currai rejects the complete event or batch instead of storing partial evidence.

Trial includes 3 completed conversations once per account, shared across workspaces. It never resets; choose a paid plan to continue.
Starter ($4/month) allows up to 1,000 events per period.
Pro allows up to 10,000 events per period.
Business allows up to 1,000,000 events per period.

Open Workspace Settings → Billing to see usage, remaining events, and the reset date. Wait for the reset or upgrade the workspace before retrying. Session creation and duplicate native event IDs do not consume the event allowance.

An intent does not match

Confirm the intent status is approved.
Describe the user language and goal that should match, not the answer the agent should produce.
Run a new real interaction after creating or changing the intent.
Use clear examples in the description when two intents are easy to confuse.
Open the linked User Story or trace to confirm the expected user message was captured.

An intent change creates a new matching version. Existing evidence remains historical; use a new interaction to validate the revised definition.

A violation does not match

Confirm the rule is active.
Write the policy as behavior the agent should avoid or verify before claiming.
Confirm the relevant agent output exists in the captured event result.
Run a new interaction that exercises the rule.
Make the rule specific enough to distinguish a violation from an allowed response.

Violation rules inspect agent output. Use an intent instead when you want to classify what the user asked for.

Slack cannot connect

Confirm the workspace is on Pro or Business. Free workspaces show an upgrade link and cannot start Slack OAuth.
Start setup from Improve → Alerts → Set Up Daily Slack Report.
Complete Slack authorization and select a workspace and channel.
If OAuth returns cancelled or failed, reopen the drawer and try again.
Ask a Slack administrator to approve the Currai app if workspace policy blocks installation.

A Daily Slack Report does not arrive

Confirm the configured alert is Active.
Confirm the Slack workspace and channel shown in Currai still exist and the Currai app can post there.
Check the report's Check every and Lookback up to values.
Confirm the lookback contains real events, intents, errors, or policy violations worth summarizing.
Wait for the next scheduled check; Daily Slack Reports are dispatched by a recurring background job.

If the connection was removed in Slack, connect it again and recreate or update the report.

Data disappeared sooner than expected

Retention is plan-based: Free keeps 3 days, Pro keeps 14 days, and Business keeps 30 days. The retention job removes data past that window. Upgrade before older evidence expires if your team needs a longer investigation period.

Still stuck

Send the workspace name, session ID, approximate timestamp, runtime, and redacted error to support@currai.app. Never send secret keys, authorization headers, full private prompts, or unredacted user data.

Review the complete start-to-finish workflow or ask the coding agent to rerun the verification steps in the Currai Skill guide.