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
- Runs — which edge fired, which constants/variables.
- Alias / subject_alias — match with Settings.
- Channel — preview vs real Telegram/widget.
- FAQ for the relevant Use Case.
- 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 — 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 |
| Email is not delivered | Channel in bot Settings | DNS/DKIM — ConnectiveOne support |
| Webhook connector / platform failure | Error edge in Runs | ConnectiveOne support |