FAQ & troubleshooting

Qalibr didn’t pick up my bug

Two things to check. First, is the report in a watched channel? Qalibr only reads the Slack channels you select (Settings → Integrations). Second, was it actually a bug? If Qalibr judged it a question, user error, or another non-bug label, it’s kept out of your backlog on purpose. See Judgment & classification.

Why is a report “Ambiguous”?

Ambiguous means there wasn’t enough signal, or the signals contradicted each other, to call it confidently. Qalibr holds it for a human rather than guessing. Add context in the thread, or make the call yourself.

Why didn’t it route automatically?

By design. Every ticket passes a human approval gate, so Qalibr prepares the report but nothing reaches your tracker until someone approves it.

It flagged a duplicate that isn’t one

You have the final say. On the report, choose Route as new instead of linking, or use the duplicate actions to link, reopen, or reject as appropriate. See Duplicate detection.

A report expired

An approval left untouched past its window expires so drafts don’t pile up. Open the Expired report and click Re-trigger to bring it back. See Re-trigger expired reports.

I hit my usage cap

Your plan meters by enrichments. Check Plan & Usage in the dashboard, and see Usage & overage. Past the cap, Qalibr only charges more with your explicit consent.

Change which channels are watched

Go to Settings → Integrations and adjust the channel selection any time. See Integrations.

Does Qalibr post in Slack?

Only where you’ve connected it, and only two things: the approval card in the thread that needs a decision, and status updates back to the original thread. It never posts in channels you haven’t connected.