Macro history shows how a macro has changed over time.
You can use it to review earlier versions, compare changes, identify where a change was made, see who made it, and start a restore or rollback from a selected version.
Open macro history
- Open Macros Management.
- Find the macro you want to review.
- Open the three-dot menu in the macro row.
- Select View macro history.
Understand the history timeline
The left side of the history drawer shows the macro’s versions in a chronological timeline, with the newest version first.
Each version card can include:
- date and time;
- source;
- version number;
- event or change summary.
Possible history events include:
- macro created;
- macro updated;
- macro reordered;
- macro deleted;
- macro restored or detected again;
- macro rolled back.
Select any version card to open its details on the right.
The history timeline does not currently include search or filters.
Review the source of a change
Each version identifies where the change came from.
The source is shown separately from the person who made the change.
Possible sources include:
- MRM for changes made through Macros Reporting and Management;
- Zendesk for changes made directly in Zendesk.
The selected-version header also describes the source, for example:
- Bulk edit in MRM;
- Created in Zendesk.
This distinction helps you understand whether a change was made through Pythia or outside the app.
Review who made the change
When actor information is available, the selected version shows who made the change.
For example, a version created in Zendesk can show a Created by field with the Zendesk user’s name.
If the actor cannot be identified, no actor field is displayed.
Review a version’s changes
For updated versions, the details panel shows semantic, human-readable changes instead of requiring you to inspect raw JSON.
Depending on the version, this can include changes to:
- title;
- active status;
- access;
- comment text;
- comment visibility;
- tags;
- brand;
- group;
- ticket form;
- assignee;
- ticket fields;
- other macro actions.
The panel can show before-and-after values or describe what was added, removed, or changed.
Examples include:
- a title before and after the update;
- tags added or removed;
- status changed from active to inactive;
- a group or ticket-field value changed.
Review the original macro version
The first version records the macro’s initial state.
For a created macro, the details can include:
- title;
- status;
- access or groups;
- actions;
- brand;
- comment visibility;
- comment text;
- tags;
- group;
- priority;
- subject;
- ticket form;
- other original values.
Long comments may appear in a shortened form with an option to view the full comment.
Review change reasons
Changes made through supported workflows in Macros Reporting and Management can include an optional change note.
When a note was provided, it appears in the selected version’s details and explains why the change was made.
Change notes are useful for:
- audit reviews;
- cleanup projects;
- troubleshooting;
- recording approvals or internal decisions;
- explaining deletions, restorations, or rollbacks.
View raw data
Each version includes an expandable View raw data section.
This section provides the technical data stored for the version and can include:
- Snapshot;
- Diff;
- Before snapshot.
You can also use Copy JSON to copy the displayed data.
Raw data is mainly useful for detailed troubleshooting or support investigations. For normal reviews, use the semantic change summary above it.
Restore or roll back from history
After selecting an earlier version, use the action button at the bottom of the drawer to start the available recovery workflow.
The button may allow you to:
- restore a deleted macro version as a new Zendesk macro;
- roll back an existing macro to the selected earlier version.
The available action depends on the macro’s current state and the selected version.
Selecting the button does not immediately update Zendesk. A separate preview and confirmation workflow follows.
Synchronisation limitation
Changes detected during synchronisation may not include every intermediate edit made in Zendesk.
For example, if a macro is changed several times between synchronisations, the history may capture the state found during the next sync rather than every individual intermediate edit.
The history drawer displays a notice when this limitation applies.