Manual Incident Logging

​

Prerequisites

• Permission to edit Incidents in the workspace
• A clear title and severity
• Optional screenshots, logs, or exports that help Anna establish the first hypotheses

​

Log an Incident

1

Open the Investigation queue

Go to Resolve → Investigation and click Log Incident.

2

Add the Incident context

Choose an optional quick-start template, then complete the form.

Field	Requirement	Purpose
Quick Start Template	Optional	Prefills a common Incident shape such as an API outage or deployment regression
Title	Required	Names the Incident in the queue and related Outcomes
Description	Optional	Records symptoms, impact, known timing, and work already attempted
Attachments	Optional	Adds up to five files, 25 MB each, for Anna to inspect during RCA
Severity	Required	Sets Critical, High, Medium, Low, or Info; the workspace default starts the field
Occurred At	Required	Records when the Incident happened; defaults to now and can be backdated up to 30 days

Add the evidence and timing Anna should start from

3

Create and investigate

Click Log Incident. CloudThinker opens the new Incident in the queue.Review the context, then click Investigate to start RCA. Manual investigation works even when On Duty (automatic investigation) is off.Success state: the Incident shows an active RCA with Context, Analysis, and Resolution phase progress.

​

What happens next

​

When to log manually

​

Next steps