Skip to content
Plaza docs

Status template — identified

Use when the cause has been identified and a fix is being prepared or rolled out.

Title

Section titled “Title”

<short noun phrase> — identified

Examples:

  • “Elevated payout latency — identified”
  • “Webhook delivery delays — identified”

Body

Section titled “Body”
Plaza has identified the cause of <symptom>.


Cause: <a one-line factual description. "An upstream RPC provider is
returning intermittent timeouts." "A recent deploy introduced a regression
in the search ranking pipeline." Avoid blame; name what.>


Action: <what we are doing about it. "Failing over to the secondary RPC
provider." "Rolling back the search deploy." "Engaged the upstream provider.">


Expected resolution: <a concrete window if we have one. "Within the next
30 minutes." Otherwise: "We will update when the action completes.">


Next update: in <30 / 60> minutes.

Notes

Section titled “Notes”
  • Confirm the cause before posting “identified”. A wrong identification erodes trust faster than slow updates.
  • It is acceptable to move from “investigating” to “monitoring” without an “identified” stop, if the action and the resolution land in the same window. Do not invent an “identified” entry retroactively.
  • Tone per AESTHETIC.md §8.