Undo a change MarqIQ applied
Undo puts back the value each field held before MarqIQ wrote to it, one record at a time, for 30 days after the set was applied. It restores a field only where that field still holds exactly what MarqIQ wrote, so a colleague’s later edit survives. If the set has not been applied yet, reject it under Approve and apply a change instead — a set that was never applied needs no undo.
Before you start
Permissions required
Undoing needs the Workspace Admin role. Anyone else gets Undoing a change set needs a workspace admin. from the server, whatever the browser showed them.
Check that the tool is still connected. MarqIQ writes the old values back through the live connection, exactly as it wrote the new ones.
Take care
Undo puts field values back. It does not reverse what your CRM did in response to the write — a workflow that fired, an email that sent, a score that recalculated, a list a record joined. Check what your own automation listens to on those fields before you rely on undo as a safety net.
Put a set back
Open Tool Operations in the sidebar.
Click the tool the set was applied to.
Change sets work in HubSpot and Marketo, so the set is under one of those two.
Click the set under History.
The list holds that tool’s 50 most recent change sets, newest first. An applied set carries the green label Applied, or the amber label Partly applied where some items were left alone. A set whose writes could not be confirmed carries Not confirmed: check HubSpot (or Marketo), and can be put back too.
Read the What happened line before you undo anything.
It counts each outcome from the apply — how many changed, how many were left alone because the value had moved, how many are no longer in the tool, how many your tool refused. An undo reads again two kinds of item and no other. The first reads Changed: your tool answered that it wrote that record. The second reads Not confirmed or Not answered: MarqIQ sent a write, or was sending one, and nothing confirms it was made. Everything else is left alone, an item that reads Not known, Not sent or Refused among them.
Click Put everything back.
The button sits above the item table whenever the set has an item of either kind. The line under it says how many changes it will read again. Where some of those are not confirmed it counts them apart and says the old value is put back on them too: MarqIQ cannot tell its own write from someone else putting the same value there, so if you put that value there yourself, change those records back by hand in your tool afterwards. It also says how many items that read Not known it leaves alone. There is no second confirmation, so read the line and the table first.
Wait for the run to finish.
MarqIQ reads the live value of every field it wrote, decides each item on its own, writes the old values back, reads the fields again and records what your tool answered. Leave the page open; a set near the 500-item cap takes a few minutes.
Read the What happened line again.
It is rewritten from the results, and it names its own denominator: “312 put back; 8 not put back because the field did not hold what MarqIQ sent.” The label at the top of the panel changes to Put back once no record may still hold what MarqIQ sent. Until then the button stays, and the label reads Applied where every item still reads Changed, Partly applied where some do, and Not confirmed: check HubSpot (or Marketo) where none does but a put-back could not be confirmed. The reason is listed above the table, under Not put back yet, and why.
Note
MarqIQ also puts its own synced copy of those records back, so the screens that read the synced copy agree with your tool without waiting for the next sync. One consequence is worth knowing: the fields are empty again in MarqIQ’s copy as well, so proposing the same operation offers the same fills a second time.
What each item does, and why
MarqIQ checks the live value of every field before it writes anything back. The decision is per item, not per set, which is why a set of 400 can finish as 312 put back.
| What the field holds now | What MarqIQ does | What the *Result* column says |
|---|---|---|
| Still exactly what MarqIQ wrote | Writes the old value back. For a fill, the old value was empty, so the field is cleared | Put back |
| Something else: changed since MarqIQ wrote, or, where MarqIQ’s own write was never confirmed, whatever your tool made of it | Leaves it alone | Not put back: the field did not hold what MarqIQ sent, with a note saying which |
| The record is no longer in your tool | Leaves it alone | Left alone: record no longer in the tool |
| Its old value already, because an earlier click’s write landed after MarqIQ had read the field | Writes nothing | Put back, with a note saying the field already held its old value |
| Your tool refuses the write | Keeps the item as it was and prints your tool’s reason under it. The button stays, so you can click again once the cause is fixed | Changed, with the reason in red. An item that read Not confirmed or Not answered before the click reads Not confirmed, never Changed |
| Your tool gives no answer to the write | Reads the field again. Where it holds the old value the item is put back; where it still holds what MarqIQ wrote the item stays as it was | Put back, or Changed (Not confirmed, for an item that was not confirmed before), with a note saying what MarqIQ saw |
| MarqIQ cannot connect to your tool, so the write never leaves | Nothing is written. The item stays as it was | Its result before the click, with a note saying to click Put everything back again |
| Your tool accepts the write, and the field still holds what MarqIQ wrote when read again | Keeps the item as changed, with a note saying so. The button stays | Changed, with the note in red |
| Your tool accepts the write and the record cannot be read again, or the field then holds some third value | Records that it could not confirm the value went back. The next click reads the record first | Not confirmed as put back, with what MarqIQ saw printed under it. An item that read Not confirmed or Not answered before the click still reads Not confirmed |
| A write MarqIQ could not confirm at the apply, and the field holds what MarqIQ sent | Writes the old value back. MarqIQ cannot tell whether that value was its own write or somebody else’s, which the line under the button says before you click | Put back |
| A write MarqIQ could not confirm at the apply, and the field holds its old value | Writes nothing | Not changed: the field held its old value when read again |
| The item was left as it was, left alone, refused or not sent at the apply | Nothing. It is not read and not attempted, whatever the field holds by now | Its original result, unchanged |
| The item reads Not known: a run before October 2026 was cut off before it kept a note for the record, or a Put everything back before October 2026 failed on it | Nothing. It is not read and not attempted, whatever the field holds: the value there may be MarqIQ’s, or may have been there all along | Not known, unchanged |
An item MarqIQ could not put back stays marked Changed. That is deliberate: the value in your tool is still MarqIQ’s, so calling it put back would be untrue. An item that was Not confirmed stays Not confirmed: a put-back that fails does not prove the first write was made.
A row that reads Left as it was: it already held this value never applied in the first place. MarqIQ did not write that value, so undo does not clear it.
Take care
Both change sets MarqIQ offers today fill empty fields, so undoing one clears those fields rather than restoring text. Your tool receives an empty value for each field, and MarqIQ reads the field again afterwards: a clear your tool accepted but did not carry out leaves the item as Changed, with a note saying the field still held what MarqIQ wrote. If something in your tool treats an empty first-touch field as a trigger, it fires on the undo.
Undoing part of a set
There is no control for choosing which records to put back. Put everything back is the whole set, and the only partiality is the partiality MarqIQ decides for itself: items whose value moved on, and records that have gone.
Where you want a subset restored, do it in your own tool. MarqIQ’s record of the set gives you the list to work from: the Person column identifies each record, the Now column holds what the field had before, and the Would become column holds what MarqIQ wrote.
The 30-day window
Undo is offered for 30 days from the moment the set was applied, not from the moment it was proposed. After that MarqIQ refuses it: This was applied more than 30 days ago. Too much will have changed on these records since, so MarqIQ no longer puts them back. Correct them in HubSpot. (or Marketo). The button is no longer shown, and the panel prints that sentence in its place.
The window is a judgement about your records, not a storage limit. MarqIQ still holds what each field was before; it stops writing that value back because a month of your team’s work has happened on top of it.
Once the window has closed, MarqIQ cannot empty those fields for you. Both change sets MarqIQ offers fill an empty field and neither clears a filled one, so a proposal cannot reverse an old fill. Correct the records in your tool instead. A change set writes no stamp field of its own, so the list to work from is the set’s own item table: the Person column identifies each record and the Would become column holds the value to clear. An import of those records with the field blank is the usual route.
The limits
- A Workspace Admin only. The refusal comes from the server, so no browser state gets round it.
- Only a set with an item that reads Changed, Not confirmed or Not answered: one labelled Applied, Partly applied or Not confirmed: check HubSpot (or Marketo). A rejected or expired set wrote nothing, and a set labelled Nothing was applied changed no record.
- A record that reads Changed is one your tool answered that it wrote. A record that reads Not confirmed or Not answered is one MarqIQ sent a write to, or was sending one to, with nothing to confirm it. Put everything back writes the old value on both where the field holds what MarqIQ sent, and for the second kind it says under the button that it cannot tell its own write from someone else’s.
- Never any other record: not one that reads Not known, Not sent, Refused, Left as it was or Not applied yet, whatever its field holds. Where records that read Not known are the only ones in doubt, the set is labelled Not known, shows no button and says why in its place. Check each in your tool, and put the old value back there by hand if it was changed.
- A set labelled Records erased from MarqIQ cannot be put back, or not any further. People it had sent a write to have since been erased from MarqIQ, so MarqIQ no longer holds those records to read or restore. The What happened line says how many changes that is, and which of them had been changed (what MarqIQ wrote stays in your tool), which were never confirmed (your tool may hold what MarqIQ sent) and which are not known (MarqIQ cannot tell whether they were sent).
- A set labelled Nothing listed was applied or No changes listed has no button either: no change it still lists was written, so there is nothing to put back.
- 30 days from the apply, per set.
- Whole sets only. No control excludes or includes one record.
- One run at a time per set. A second click while a run is going gets Someone else has just started this. Reload to see where it stands. or A run is under way on this change set. Reload to see where it stands.
- A workspace may take 30 change-set actions a minute, counting approve, reject, apply and undo together.
- An AI assistant can never undo a set. It has no route that does.
If it did not work
The message reads Undoing a change set needs a workspace admin.
Why: You are signed in under another role. Applying and undoing are the two change-set actions checked against the Workspace Admin role on the server.
Fix: Ask a Workspace Admin to undo it, or have your role changed under Team & roles.
The message names the 30-day limit
Why: More than 30 days have passed since the set was applied.
Fix: Correct the records in your tool, working from the set’s own item table. A change set adds no stamp field, so there is nothing in HubSpot or Marketo to filter a list on; the Person and Would become columns are the record of which records MarqIQ touched and what it wrote. In HubSpot you can confirm any one of them from the property history on the contact, which names the private app that wrote.
The message reads Only a change set that was applied can be undone.
Why: The set is waiting for approval, approved, rejected or expired. No run has ended on it, so nothing is there to put back.
Fix: Read the label at the top of the panel. A set that is still waiting is stopped by clicking Reject, which needs the Workspace Admin role or Manage on Tool Operations.
The message reads Nothing was applied, so there is nothing to put back. or This change set has been put back, so nothing is left to put back.
Why: No record of the set may still hold what MarqIQ sent. Either the apply changed nothing, or an undo has already finished.
Fix: Nothing. The panel shows no button on such a set; the message comes only from a request made another way.
The message reads Put everything back is not offered for the … that are not known
Why: Every record in doubt on this set reads Not known. Either a run before October 2026 was cut off before it kept a note for them, or a Put everything back before October 2026 failed on them and its answer replaced the note of what the apply had done. Either way MarqIQ cannot tell whether it wrote to them, and it puts back only what it knows it sent.
Fix: Check each of those records in your tool, and put the old value back there by hand if it was changed. In HubSpot the property history on the contact names the private app that wrote each value.
The label reads Nothing left to put back
Why: An undo ran and found no record it could put back: each one held something other than what MarqIQ sent, had gone from your tool, or already held its old value. MarqIQ does not call that Put back, because it put nothing back.
Fix: Read the Result column for the reason against each item, then decide which records to correct in your tool.
The label reads Records erased from MarqIQ
Why: The set was applied, and people it changed were later erased from MarqIQ at a privacy request. The erasure removes their rows from the set, so MarqIQ can no longer read those records or put them back. What it wrote to them is still in your tool. Where only some were erased, Put everything back still puts the others back; the label then reads Records erased from MarqIQ, not Put back, and the What happened line counts both.
Fix: Correct those records in your tool if they need it. The What happened line says how many changes are no longer listed.
The label reads Not confirmed: check HubSpot (or Marketo) after the undo
Why: For some records your tool accepted the old value or gave no answer, and MarqIQ could not read them again to confirm it. They may be put back, or may still hold what MarqIQ wrote.
Fix: Click Put everything back again. MarqIQ reads those records first: one that holds its old value becomes Put back with nothing written, and one that still holds what MarqIQ wrote is sent the old value again.
Many items read Not put back: the field did not hold what MarqIQ sent
Why: Those fields held something else when the undo read them. Somebody, or one of your own workflows, changed them after MarqIQ wrote. Or MarqIQ’s write was never confirmed, and a workflow of yours rewrote the value as it arrived. The line under each result says which. An undo never writes over a value MarqIQ did not send.
Fix: Nothing, unless you want those particular values changed. Decide record by record from the table, and make the changes in your tool.
Some items still read Changed with a message in red
Why: Your tool refused the write back: a limit on calls, a sign-in that no longer works, a read-only field, a validation rule, or a required field left empty by the clear. The button stays, and the reason is also listed once above the table.
Fix: The message says what to do. For a limit, wait until it resets. For anything else, give the message to whoever administers that tool. Then click Put everything back again: MarqIQ reads again only the records that may still hold what it sent. The value in your tool is the one MarqIQ wrote until then.
Nothing was written and the message names the tool
Why: Your tool would not return the current values, so MarqIQ stopped before writing anything. The message ends with Nothing was changed.
Fix: Check the connection under Connected Tools, reconnect if it asks you to, and click Put everything back again. Nothing was changed, so there is nothing to clean up.
The set has read Applying… for a long time
Why: The run was cut off part-way. A run is allowed five minutes; a set still on Applying… a minute after that is read from its items instead of waiting on a run that is over.
Fix: Reload after six minutes. What the run put back reads Put back, and what it did not still reads Changed, so Put everything back is offered again for the rest.
The label reads Partly applied after the undo, and some rows still read Changed
Why: Either the run reached its limit (one run stops starting new work after 150 seconds) or your tool refused or did not answer for those rows. What was put back reads Put back. The rows that were not still hold what MarqIQ wrote, and each says why underneath.
Fix: Click Put everything back again, after fixing whatever a red message names. MarqIQ reads again only the records that may still hold what it sent.
The label still reads Applied after the undo finished
Why: No item was put back and every item still reads Changed: your tool refused each write back, or did not answer while the fields still held what MarqIQ wrote. The reason is above the table, under Not put back yet, and why.
Fix: Fix what the reason names, then click Put everything back again.
The message reads Too many actions in a minute.
Why: A workspace may take 30 change-set actions a minute.
Fix: Wait a moment and click again. Nothing was changed by the refused attempt.
Next steps
Related articles
Was this article helpful?