Declarative agent consistently responds with "Something went wrong. Try again later." when generating slides

The behavior matches a backend/service issue or a policy/limitations change in declarative agents rather than anything in the agent instructions.

From the available information, only the following supported actions are possible:

1. Treat “Something went wrong. Try again later.” as an internal service error
   • This error is documented as an internal service error that requires support if it persists.
   • Because it occurs consistently when the agent tries to generate slides, and the same agent still works in “Try it” (but without the template), this strongly indicates a platform-side problem or a change in what is allowed in that interaction surface.
   • No configuration-side fix is documented for this error beyond retrying and contacting support.
2. Check for new or changed admin policies affecting the agent
   • Declarative agents can become non‑updatable or non‑compliant when new admin policies are applied. In those cases, a banner appears and the agent cannot be updated until the sharing/usage settings are changed.
   • If any new policies were recently applied (for example, around sharing, sensitivity labels, or allowed actions), adjust the agent’s sharing and configuration to a compliant option and republish.
3. Verify sharing and access to any knowledge sources or files used in the slide generation
   • If the agent relies on SharePoint/OneDrive files (for templates, agendas, or other content), ensure:
     • All users invoking the agent have at least read access to those files and locations.
     • The files are not blocked by unsupported sensitivity labels.
   • If sharing fails or is incomplete, users may see generic runtime errors and the agent may not be able to use the expected resources.
4. If the error persists, open a support case
   • “Something went wrong” is explicitly documented as an internal service error with no self‑service workaround beyond retrying.
   • Since the issue is persistent across days and the agent previously worked, the next step is to contact Microsoft support with:
     • Tenant ID
     • Agent ID/name
     • Time stamps and correlation IDs (if visible) for failed runs
     • Description of the regression (first click vs second click behavior, and loss of template usage in “Try it”).

There is no documented configuration change that restores the previous “clickable PPT in template on first try” behavior when this specific internal error appears consistently. Resolution requires platform-side investigation by Microsoft support.

References:

• Share and manage agents
• Known issues
• Generative answers pointing to SharePoint sources don't return results
• Declarative agents FAQ