Media request failed

Symptoms

An image, Office document, or generated-media request is rejected, omits media output, or fails during transfer.

Check

1. Identify the exact workflow: image/Office understanding or image generation.
2. Check that the selected model/service supports that media capability and that the model route targets it.
3. For media generation, confirm the selected eligible route was saved and enabled, and all enabled targets support MediaImage.
4. Check request history for input validation, provider, or transfer errors; verify any required artifact URL/storage can be reached by the participating client.
5. Keep source files and generated assets private while investigating.

Resolution

Use a model route with the required capability, correct the saved generation target or storage reachability, and retry once with a small permitted input. A successful config save does not prove the model generated media or that a client can download it.

Escalate if still stuck

Record the workflow, model/service, request stage, and sanitized error. Do not attach private media or signed URLs. See Media understanding , Media generation , and Diagnostics .