---
title: "Report a problem to the Telegram-Auto team"
locale: en
url: https://tlg.builera.app/en/docs/agent-playbooks/report-a-problem
verified: 2026-10-27
app_version: "2.3"
---

# Report a problem to the Telegram-Auto team

When you hit a bug, a cumbersome step, a missing capability or have a question, file one short ticket without secrets, then follow the answer.


## Goal

You tell the Telegram-Auto team about a bug, a cumbersome step, a missing capability, a docs gap or a question — so the team improves the app, not to do the user's work.

## Permissions needed

- Scope `feedback` (on for new connections; the user can turn it off). `whoami` shows it at `support.feedback_enabled`.
- Every connection role can use it, viewers included.

## Ask the person before

Ask before putting any of their business data in a ticket (customer names, message text, group names). You do not need to ask to report your own technical failure.

## Check first

1. Call `feedback.list` to see whether a ticket for this problem exists. If so use `feedback.append`, do not create a new one.
2. Keep the `trace_id` of error answers (up to 5, within 7 days, same connection).

## Steps

1. Call `feedback.create` with:
   - `category`: `bug`, `tool_friction`, `missing_capability`, `docs_gap`, `question`, `improvement`, `praise`, `security` or `other`.
   - A short `title` (≤ 160 characters) and a concrete `description`: what you did, what you expected, what you saw.
   - If known: `related_operation` (operation code), `related_trace_ids`, `expected`, `actual`, `steps_attempted`, `workaround`, `impact`.
2. Keep the returned `ticket_id` (`TG-FB-XXXXXXXX`). If `deduplicated: true`, the existing ticket counted one more occurrence.
3. Tell the person in one sentence which ticket you filed and about what.

> [!IMPORTANT]
> Never put in a ticket: passwords, login codes, 2FA codes, API or bot keys, Telegram sessions, cookies, proxies with passwords, card numbers. A ticket with any of them is refused whole (`feedback_secret_detected`) and nothing is stored.

## Check after

- `whoami` shows tickets with new answers at `support.tickets_with_updates`. When above 0, call `feedback.list` with `updated_since`, then `feedback.get`.
- Status `waiting_on_reporter` means the team asks something: answer with `feedback.append`.
- Do not poll in a loop; read again at most once every 60 seconds.

## When it fails

| Code | Meaning | Do |
|---|---|---|
| `feedback_disabled` | The user turned the channel off for this connection | Stop and tell the person |
| `feedback_secret_detected` | The ticket contains something secret-like | Remove it (see `details.rejected`) and send again |
| `feedback_quota_exceeded` | Over a limit | Wait until `retry_at` |
| `feedback_intake_paused` | The team paused intake | Try later, nothing is lost |
| `feedback_closed` | The ticket is closed | File a new one if the problem is still there |

## Stop when

Stop once you have a `ticket_id` and told the person, when the person does not want to send, or when the channel is off.