Problem Diagnostics

Summary

If the problem is described only generally, for example "doesn't work", collect context first:

what project;
what section;
what channel;
what agent;
what kind of lead or dialog, if any;
what the user clicked;
what is the error text;
when did this happen;
whether the user changed the settings recently.

Many error messages include a For support action. It copies a clear error description, HTTP status, failed API request method and address, current page, time, and technical details. Send the complete text to support so they can distinguish an access problem, invalid data, and a temporary server failure. Retry runs the failed action again.

For agent problems

activity;
published version;
purpose;
keywords;
instructions;
model;
balance;
MCP;
variables;
generation history.

For payment problems

payment settings;
country and currency;
payment system;
order ID;
payment status;
transaction history;
credit history.

For access problems

project role;
access to channels;
invitation activity;
correct account;
login method;
whether the participant has been removed from the project.

For import/export/migration issues

open "Processes";
check the status;
open details;
transfer the process ID to support.

Where this is in the interface

Main elements in this section:

close error button
copy data button for support
hide error button
reload button after error
project sidebar
project settings page
Settings item in the side menu