Troubleshooting
Find the failing step and get feedback flowing again.
Start with the path a report takes: registered application, connected source, submission confirmation, then the inbox. Checking each step helps distinguish a connection problem from a hidden report.
Check the source connection and any pending approval. Start with the channel's setup instructions.
Open integration setupA complaint is missing
- Confirm that the channel reported a successful submission. An approval request is not a success confirmation.
- Open Complaints and clear search, date, source, category, and severity filters.
- Check both Open and Resolved.
- Confirm the application selected by the widget or linked repository, or the name supplied by the sender.
Avoid resubmitting while the first request is still in progress. Repeated submissions can create separate reports.
Application not found
Copy the registered name from Applications. Matching is case-insensitive, but punctuation and spacing still matter. Register the application before sending a report.
For a widget, regenerate the embed snippet after changing the application name. For GitHub, check the repository's linked application.
An AI agent cannot see the tools
Check the endpoint in AI agent setup. Use a client that supports Streamable HTTP for the remote connection, then reload its MCP configuration. Ask the client to list available tools and look for report_complaint.
If using the local stdio package, inspect the client's server logs and confirm it can run the configured command.
The widget does not appear
- Confirm the page loads
widget.jssuccessfully in the browser's Network panel. - Confirm
data-appcontains a registered application name. - Install the script once in the page shell, not once per route.
- Check for blocked scripts or restrictive host-page policies in the browser console.
The setup preview does not send real reports. Test the installed widget on an actual page.
A bot does not respond
| Channel | Check |
|---|---|
| Telegram | Open the bot and press Start. For workspace access, use the account-linking button inside Complaintr. |
| GitHub | Confirm the repository is installed and linked. Mention @complaintrbot in an issue or pull request comment, including approval replies. |
| Send a direct message to the Complaintr account. Comments and mentions do not start the DM flow. |
If a summary is waiting for confirmation, give a clear yes or no. See Integrations for each channel's setup.
Telegram alerts are missing
Check that Connection shows Connected and New complaint alerts is enabled in Integrations > Telegram. Confirm that you have not blocked the bot. Test with a newly submitted complaint.
Too many requests
A 429 response means a rate limit was reached. For HTTP complaint submissions, use the Retry-After response header before retrying. Do not retry in a tight loop. Current submission limits are documented in the API reference.
A service is unavailable
A maintenance notice or temporary service error can prevent a channel from responding. Wait and retry after the service returns. If the problem continues, contact the workspace or deployment administrator with the time, channel, and error message.
Ask for help
Use Contact and include:
- The channel and the step that failed.
- The approximate time and timezone.
- The error message or HTTP status.
- What you expected and what happened instead.
Remove credentials, tokens, and private customer information from screenshots and logs.