Troubleshooting

This page is for the moments when nicoolAI did not do what you expected.

The goal is not to explain every internal detail. It is to help you recover quickly and report the right context if you need help.

nicoolAI did not reply

What it usually means:

• the message never reached a supported channel path
• the runtime could not process the message successfully
• the system was temporarily unavailable or rate-limited

What to do next:

• retry once
• confirm which channel you used
• if it still fails, note the channel and approximate time of the message

nicoolAI cannot access a connected tool

What it usually means:

• the connector was never fully connected
• the saved credentials expired
• the wrong linked account is being used
• the connector exists, but this exact workflow is not exposed yet

What to do next:

• reconnect the tool
• confirm you are using the expected linked account
• try again after reconnecting

If the failure involves Google Drive, also check whether the document type is one of the supported formats.

nicoolAI cannot access Slack files or attachments

What it usually means:

• the Slack app is missing the permission needed for private file metadata or downloads

What to do next:

• review the Slack app scopes
• if the failure involves private file metadata or downloads, suggest files:read first

Only add more Slack scopes when they map to a capability the product actually uses.

nicoolAI did not send an email

What it usually means:

• the email channel and the email connector are being confused
• outbound sending is not configured for the account
• SMTP credentials are missing or invalid

What to do next:

• confirm whether you expected a channel reply or connector-based sending
• recheck the relevant email setup
• if sending is not configured, fall back to drafting the email in chat

nicoolAI says it cannot do something it used to do

What it usually means:

• you are now in a different channel, workspace, or thread scope
• the connector is no longer active
• the feature is restricted to a role or context you do not currently have

What to do next:

• confirm you are in the same channel and account context as before
• check the relevant connector status
• check whether the request now sits inside a different trust boundary

The response feels too cautious

What it usually means:

• nicoolAI is intentionally narrowing because the request is ambiguous or under-scoped
• the system does not have enough permission or context to act safely

What to do next:

• be explicit about the action you want
• name the connector, account, or channel if it matters
• say whether you want a draft, a recommendation, or a real action

What to include when reporting a problem

Share the smallest set of details that makes the failure diagnosable:

• which channel you used
• when it happened
• which connector was involved, if any
• what you expected to happen
• what nicoolAI actually did instead

When to escalate instead of retrying

Escalate when:

• the request involves sensitive data or approval
• the system should clearly have access but keeps refusing
• the same failure repeats across retries

Related pages

• Channels
• Email Channel
• Connectors
• Security
• Channels and integrations