<!--
ARTICLE TYPE: Troubleshooting
USE WHEN: The reader has a symptom and needs to diagnose and resolve it.
DELETE THESE GUIDANCE COMMENTS AS YOU WRITE.
-->

<!--
TITLE: Name the symptom in the user's words.
"Can't log in to Workday"
"Outlook won't open on company laptop"
"Print job stuck in queue"
The user is searching for their symptom, not for the cause.
-->

<!--
SCOPE STATEMENT — REQUIRED.
-->
This article applies to [audience] experiencing [symptom].

## What you might see

<!--
List the actual symptoms the reader is encountering. Use plain user-facing language.
"Your screen shows a red banner that says 'Authentication failed.'"
NOT: "The IdP returns a 401 response."
This helps both the reader confirm they are in the right article and helps Hubert match
the user's query to this article.
-->

- [Symptom 1]
- [Symptom 2]
- [Symptom 3]

## Try these in order

<!--
Steps go from cheapest/most likely first to most involved last.
Each step is a self-contained attempt. After each, the reader knows whether they are done.
-->

### 1. [Most common cause — short label]

[What to do, in one to three steps.]

If that resolved it, you are done. If not, continue.

### 2. [Next most common cause]

[What to do.]

If that resolved it, you are done. If not, continue.

### 3. [Less common cause]

[What to do.]

## When to open a ticket

<!--
Be explicit about the boundary. The reader has tried the steps above. When does this
become a support team problem?
-->

If none of the steps above resolved the issue, open a ticket and include:

- [What information to provide: screenshots, error message text, time of occurrence, device]
- [Ticket type or category to select]
- [Link to the ticket form]

## Related articles

- [Related article]

<!--
METADATA TO SET IN SERVICENOW:
- Short description: name the symptom and the resolution path
- Category / KB topic: from existing taxonomy
- Keywords: symptom phrases, error message text, app names — exactly what a frustrated user types
- Audience: who this applies to
- Owner: named person or team (typically the support team that owns the affected system)
- Last reviewed: today's date
- Review cycle: quarterly recommended — symptoms and fixes change with system updates
-->
