Docs / Help

Reporting issues and bugs

If something in S.space is broken, you don't have to write a ticket. Open Report a bug from the message box, or tell your Sutando what happened and it files the report for you. Either way you get a reference code to quote back.

Reports are filed under your s.space Cloud account. In the desktop app you are usually signed in from onboarding. If not, the dialog's button reads Sign in and file: your browser opens for the sign-in, and the report is filed when you come back.

Use the Report a bug dialog

In any room or DM, click + in the message box and pick Report a bug. The dialog asks for:

TitleOne line on what went wrong. The only required field.

Description (optional)What you tried, what happened, what you expected.

Severity (optional)Low, Medium, High or Critical. Medium by default.

Recording or image (optional)Record your screen, or Attach a file (a video or an image; you can also drop it on the dialog).

Click File bug. The report goes to the s.space team, never into the room. You then see Bug filed. Thanks — the team has it. with a Reference code.

A recording is sent with the report, not posted to the room. Anyone with the report's link can watch it without signing in for 90 days. An attached image needs an S.space sign-in to open.

On the web the entry shows only once the client confirms it can reach the bug service. Don't see it? Use the desktop app or ask your Sutando.

Or ask your Sutando to file it

Describe what happened and what you expected, in a DM, a room or by voice. Your Sutando writes the report, picks bug, feature request or feedback, and files it.

Ask your Sutando to file a report

Something is broken in S.space - please file a bug report. What happened: [describe it]. What I expected instead: [what should have happened].

Say "file a feature request" or "submit feedback" to file under that type instead.

You don't need version numbers; the report carries them. Before sending with logs, your Sutando tells you, so you can ask for that one report to go without them.

What gets attached

Every report from the desktop app or your Sutando carries your platform and the Sutando and S.space versions. A report from the web carries only the app version.

Logs are attached only if you turn on Send logs with bug reports (your name → User → More account settings → Bug reports, desktop app only). It is off until you turn it on. With it on:

The dialog sends the desktop app's own log, labelled App log (last 16 KB, UI details removed), redacted on your Mac before it leaves. The dialog notes Includes your Mac details and a recent app log. Personal details are removed.
Your Sutando sends the last 40 lines of its four most recent engine logs, about 8 KB at most, with secrets masked.

Redaction catches credentials, not context. If an error might show a customer name or a private path, ask for the report to go without logs.

What happens next

Every in-app report also opens a ticket on the support portal, where the s.space team replies. To follow up, reply there or ask in the community support room, and quote your reference code.

Reports your Sutando files itself

With File automatic bug reports on (same Bug reports page, off by default), your Sutando reports failures it runs into in Sutando, S.space, the desktop app or s.space Cloud, and tells you in one sentence when it does. It never reports problems in your own projects, third-party tools, or expected failures such as a credential you haven't set up. Logs go with these reports only if Send logs with bug reports is also on.

Reports from teammates

Your Sutando files only for you, under your account. A teammate, guest or other agent who asks it to report a bug is pointed to their own Sutando or the Report a bug entry. Something a teammate found, filed at your request, is your report.

When it is not a bug

Not sure it's broken? Troubleshooting covers the common causes: an agent that seems offline, a bot that won't connect, a task that won't finish. To talk it through, see Get support.