Activity and Usage answer two different questions: what work did MazeGraph record? and how much model usage did it produce? Activity helps you inspect site changes, operational events, and work that continued in the background. Usage summarizes messages and tokens over time. These records help with review and troubleshooting; they do not replace your provider’s billing dashboard.
Review Activity
Open MazeGraph → Activity to review three kinds of records:
| Activity section | What it contains | Useful for |
|---|---|---|
| Changes | Recorded site changes, their applied or undone status, the source, and any related session. | Checking what changed and undoing an eligible change you made. |
| Plugin logs | Filterable operational events such as runs, model calls, tool decisions, and system activity. | Finding when a request or tool action was refused, delayed, or completed. |
| Background work | Background replies and scheduled maintenance, with status, attempts, and last activity. | Seeing whether work that continued after the chat is still running or has finished. |
You can filter changes by All, Applied, or Undone, and filter plugin logs by event. People who manage MazeGraph can switch between Mine and Everyone’s records; other users see their own scope. A manager can review another person’s change, but only the person who made an eligible change can undo it. See Review changes and undo for details.
Activity stores limited operational details. It does not record chat message text, tool arguments or results, or provider keys. This lets you review events without turning the log into a transcript. To manage how long event logs remain, see Limits and privacy settings.
Understand Usage
Open MazeGraph → Usage to choose a 7-, 30-, or 90-day view and review tokens sent, tokens received, and messages. The daily chart uses UTC and includes today’s partial totals. People who manage MazeGraph can view the Whole site or Only mine; other users see only their own usage.
The report can also show usage by person and estimated provider costs. Cost estimates use published input and output rates for models with a matching rate; models without one are excluded. Rates and provider billing can differ, so use the estimate as a comparison aid and check the provider’s own account for actual charges. You can download the report as a CSV. For a closer guide to the report, see Understand Usage totals.
Retention and personal data
Session retention is off by default, so conversations remain until a person deletes them or an administrator sets a retention period. Operational event logs default to 7 days and can be configured from 7 to 365 days. Daily Usage summaries can remain for up to 400 days. These are separate records with separate retention behavior.
Clearing the operational event log removes Plugin logs; it does not remove sessions, recorded changes, or background jobs. To process a person’s MazeGraph data through WordPress export and erasure, see Export and erase personal data. Administrators can also enable or disable the Activity and Usage areas in Tools → Extensions.
If a record or total is missing
| What you notice | Likely reason | What to check | How to prevent confusion |
|---|---|---|---|
| You cannot see another person’s Activity or Usage. | Your account may not have permission to manage MazeGraph, or the report is set to Mine / Only mine. | Ask a MazeGraph manager to review the whole-site view or your access. | Remember that a user’s personal view is limited to their own records. |
| Activity or Usage is unavailable. | An administrator may have switched its module off. | Check MazeGraph → Tools → Extensions or ask a manager to check it. | Keep only the areas the site intends to use enabled, and tell the team when availability changes. |
| Changes remain after Plugin logs were cleared. | Change records and operational event logs are stored and retained separately. | Review the Changes section, session deletion, and retention settings for the record you want to remove. | Choose the relevant record type before clearing data; clearing logs is not a full Activity or data erasure. |
For request limits and their effect on new work, see Usage limits. For site access and roles, see Availability and role access.