---
title: "When the problem is not in the scenario"
description: "Self-debug: what to check in the scenario first, and when to contact ConnectiveOne support."
---

# When the problem is not in the scenario

Short reference: what to check in the scenario **first**, and when the task is outside this track.

## Algorithm

1. **Runs** — which edge fired, which constants/variables.
2. **Alias / subject_alias** — match with Settings.
3. **Channel** — preview vs real Telegram/widget.
4. [FAQ](/en/learn/implementer/training/reference/faq.md) for the relevant Use Case.
5. If the scenario is correct but platform behavior is inconsistent — **ConnectiveOne support**.

## Symptom → where to look

| Symptom | First in the scenario | Outside the scenario |
|---------|-----------------------|----------------------|
| Report / analytics does not show data | `statistic__set`, Custom Data write in Runs | Analytics outside Scenario Builder — ConnectiveOne support |
| Operator does not see the dialog | `subject_alias` in connect | [Operator Panel](/en/operatorline/integrator-hub.md) — subjects, operators |
| Transfer in the panel does not work | Connect success in Runs | OP documentation — transfer is not a scenario |
| Skill groups / shift schedule | Different `subject_alias` | Settings → OP — check subject settings |
| Permissions / module missing from menu | — | [Roles](/en/settings/how-to/configure-roles.md) |
| Email is not delivered | Channel in bot Settings | DNS/DKIM — ConnectiveOne support |
| Webhook connector / platform failure | Error edge in Runs | ConnectiveOne support |

## Related materials

- [FAQ](/en/learn/implementer/training/reference/faq.md)
- [General debug](/en/learn/implementer/training/reference/faq.md#general-debug)
- [Integrator overview](/en/learn/implementer/implementer-overview.md)