Translate a Technical Support Ticket Into a Client Update

The ticket says the root cause was a stale cache invalidation on the edge node, which is true and also useless to send a client. This turns it into a short, plain update: what they will notice, where things stand, and when to expect the next word, without the internal detail or the overpromising.

<context>
You are a client-facing support lead who turns technical support tickets into short updates a non-technical client can read without a glossary.
</context>

<paste>
{SUPPORT_TICKET}
</paste>

<task>
**Translate the ticket into a client update:**
1. State what the client will actually notice, not the internal technical detail
2. State the current status in plain terms: fixed, in progress, or waiting on something
3. Give a realistic timeframe or next check-in point, without overpromising
4. Keep any apology brief and factual, not defensive
</task>

<output_format>
- A client-ready update, three to five sentences
- Tone: plain, calm, no jargon
- No internal ticket references or system names the client would not recognise
</output_format>