Start with the exact message MazeGraph shows, then check whether the problem affects one person, one tool, or the whole site. The symptom table points to the first useful place to look.
Find the right guide
| What you notice | Start here |
|---|---|
| MazeGraph cannot get a reply, or the selected model is unavailable. | The provider is unavailable: check WordPress Settings → Connectors, connected model availability, and the selected text model. |
| A tool is missing, unavailable, or refused. | A tool is missing or refused: review site availability, the tool switch, assistant access, WordPress role permissions, and policy checks. |
| Content Studio cannot create or update a WordPress draft. | Content Studio will not hand off a draft: check your post permissions, chosen content type, taxonomy selections, editor lock, and whether the post changed. |
| An AI app such as Claude Code or Cursor cannot connect over MCP. | An MCP app cannot connect: check the server switch, the address, the connection key, the account’s role and the rate limit. |
| A reply is slow or continues after you leave the chat. | Check request timings and background work in Activity. |
| A reply stops at a usage or response limit. | Review Usage limits and the site’s current Usage report. |
| You want to know what data is sent to a provider. | Read Data and privacy and What a provider request may contain. |
Check what happened before trying again
Open MazeGraph → Activity to see whether a reply, tool call, background task, or site change was recorded. Activity can help distinguish an action that failed from one that completed before the interface showed an error. It does not contain conversation text, tool arguments or results, or provider keys. For a change that might have written to WordPress, inspect the post and Activity record before repeating the action.
If the problem is connection or site availability, open MazeGraph → Settings → About and review the status cards. Check the provider connection in WordPress Settings → Connectors, then confirm that the default or session model is still offered by that connector.
Collect details for support
In MazeGraph → Settings → About, open Installation diagnostics and select Copy diagnostics. The summary includes software versions, provider and model status, tool state, limits, context strategy, retention, and MCP sharing status. It excludes API keys and conversation text. Review the copied details for site-specific information before sharing them.
For a slow reply, an administrator can temporarily turn on Collect request timings in MazeGraph → Settings → General. The chat composer will show browser timing details; required requests continue to run whether this option is on or off. Turn it off after collecting the information you need.
When you ask for support, include the MazeGraph, WordPress, and PHP versions; which page and action were involved; whether the issue affects one person or everyone; and the exact error text with private details removed. Do not include provider keys, passwords, private customer information, or a full conversation unless the person who owns that data has authorized sharing it.
Example: a tool is refused
What happened: A tool is listed but MazeGraph refuses to run it. Reason: A site-wide availability switch, individual tool setting, assistant access list, WordPress capability, usage guardrail, or stricter policy rule may block the call. Solution: Check each layer in A tool is missing or refused and ask a site manager to change the setting that applies. Learning: The session’s Ask, Auto, or Full permission mode does not enable a disabled tool or bypass WordPress permissions and guardrails.
For further help, visit MazeGraph support on WordPress.org.