Managing bugs, connected logs, and demo times

1. 1Search all reports or filter by type, status, and source. Use Next reports for older results.
2. 2Open a report to assign staff, set its severity, write private investigation notes, or link it to a roadmap item. Response visible to the reporter is saved in their account, not emailed.
3. 3Expand diagnostic samples to inspect the failure and recent actions. Export JSON downloads the investigation record.
4. 4For a known temporary problem, set Mute until and Mute reason. Samples still collect, but recurring alerts and automatic reopening pause until that time.

Ingestion, alerts & demo settings

• Log sources: enable a supported provider connection or create a private receiving key. Missing connection details and rejected requests are shown here. Creating a key alone does not connect an outside service. Use Sync now or Replay 24 hours to check a poller.
• Policy: choose which expected failures to ignore, how many samples to keep, when repeated problems become critical, and when to send alert emails.
• Noise rules: ignore automatic failures matching a source, title, or response number. Manual customer reports are never silently discarded.
• Source maps: upload matching build files so stack traces show the original file and line. These files are private.
• Critical alerts: inspect delivery errors and press Retry alert after fixing email settings. The top-bar Alerts button also shows critical problems immediately.
• Demo bookings: add future meeting times and an optional secure meeting link. Visitors must confirm by email. Cancel a booking to release its time and close its suggestion access.