Identify the affected service
Chat, images, video, voice and music place different demands on our services. Being able to open the homepage does not mean every generation function is available. A failed request in one function does not establish that the whole platform is down, either. Identify what you were trying to do and whether the same problem happens again before drawing a wider conclusion.
Put a notice in context
A useful service report names the affected function and says when the information applies. Queue length, uptime and response time are measurements; a loading message cannot supply them. Compare any service notice with the behavior you can reproduce. If the problem keeps returning, use our troubleshooting guidance to work through account and browser checks alongside the service information.
Send the steps, not your credentials
For a support report, note the time, the action, the affected media type and the wording of any error. Include your browser and device, and whether another browser behaves differently. Never send passwords or session tokens. These details help us distinguish an account issue, an individual failed generation and a broader service interruption.