Support, troubleshooting, and known issues

When to stop retrying and escalate

Some support issues improve with one more careful attempt, but others should escalate before more self-serve effort creates noise or risk.

Who this is for: Users deciding whether another self-serve attempt is useful or whether it is time to escalate.

Last reviewed 2026-04-30 · Source of truth: broader help library · Languages: en, es

Article metadata

Product area: support and escalation

Owner: Support operations

Parity reviewer: Bilingual launch review

Retrieval-ready: Yes

What to expect next

Escalate once another attempt would mostly create repetition instead of new signal.
Use restricted or narrower lanes when the issue is sensitive, not just frustrating.

Retry when the path is still clear

A careful retry can still make sense when the next step is canonical, low-risk, and clearly described by governed help.

Examples include re-reading a launch article, using a clearer intake category, or confirming a visible route choice.

Escalate when more retrying adds risk

Escalate when the task is already blocked, the next step is ambiguous, or the issue touches identity, billing, migration consequences, or other trust-sensitive surfaces.

Do not keep retrying when the real problem is lack of certainty rather than lack of effort.

Escalation path

If the issue is blocked and the next attempt would rely on guesswork, that is your signal to escalate.

Related next steps

Read how to report a blocked task clearly Open structured support intake Open Spanish version Back to help center