The Change history is the register of the operations carried out on the event by the members of the team and by Nightify staff. It is used to reconstruct who did what and when, for example when an event turns out to be suspended, a review has been cancelled or a draft has been deleted. The Operation column does not show the name of the button but the technical code of the action: the table below translates them.
At a glance
- Where: Event dashboard → Change history tab. The page is titled Change history event #….
- Permissions: View event logs, included among the predefined roles only in Administrator.
- What you get: the complete, unpaginated list of the operations, most recent first, with date and time, author and code of the operation.
Step by step
- Open the history. From the dashboard of the event choose the Change history tab. What you see: a table with the columns Date, User and Operation.
- Read the rows. The first row is the most recent operation. Date shows date and time with the seconds; User the first name, surname and e-mail of the author; Operation the technical code.
- Interpret the code with the table below and, if you need to, compare it with Last update and Updated by in the status card of the dashboard.
Fields and options: the codes of the Operation column
| Code | What it means | Who generates it |
|---|---|---|
disable | Publication suspended (Suspend publication). | Team of the organization. |
enable | Publication re-enabled (Enable publication). | Team of the organization. |
submit_pending | Event or changes submitted for review (Publish event / Publish changes). | Team of the organization. |
cancel_review | Review cancelled (Cancel verification and return to draft). | Team of the organization. |
update_snapshot | Draft save: it is recorded at every save of the contents (texts, prices, images and so on). The row says that a change took place, not which field changed. | Team of the organization. |
delete_draft_snapshot | Draft of the changes deleted (Delete draft on the status card). | Team of the organization. |
map_create and update_snapshot_event_map_assignment | Creation of the seat map and assignment or modification of the map in the draft. | Team of the organization. |
snapshot_access_type_missing | Report of an access title missing from the saved version. | System, during the ticketing operations. |
duplicate | Event duplicated (Duplicate). | Team of the organization; the row appears on the source event. |
review_admin_approve, review_admin_retry_ticketing_sync, finalize_staged_snapshot_approval | Approval of the review, new attempt at synchronising the ticketing and finalisation of the approval. | Nightify staff. |
insert, delete_draft | Insertion of the event and deletion of the draft by the administration. | Nightify staff. |
What it does not contain
- The detail of the fields that changed: to compare the contents, open the draft and the published version from the editor of the event.
- The actions on the reservations (cancellations, regenerations, changes of the holder), which you find in the detail of each order, and the scans, which are in the Entries report.
- The written outcome of the review: the reason for a rejection is in the status card of the dashboard, under Reason for rejection:.
Messages and errors
| Message | Why it appears | What to do |
|---|---|---|
| Empty table | No operation recorded for the event. | Normal for an event that has just been created and never saved or submitted. |
| The Change history tab does not appear | The role does not have View event logs. | Ask an Administrator. |
Many update_snapshot rows close together | Every save of the draft generates a row. | No action: this is the expected behaviour. |
Special cases
- The event turns out not to be published and you do not know why: look for the last
disablerow and read the User column. - A review has disappeared: a
cancel_reviewrow means that a member of the team cancelled it, taking the event back to draft. - You want to know who created the copy of an event: the
duplicaterow is on the source event, with the author.
Rules and limits
- The history is read-only and cannot be deleted or filtered.
- The list is complete and ordered from the most recent; it is not paginated.
Related articles
- Pause or reactivate publishing
- Submit the event for review
- Cancel the review and return to draft
- Duplicate an event