Approve and apply a change
Approving says the list is right. Applying is the moment MarqIQ writes into your CRM, and it re-checks every record against the live value first. If the set is not yet built, start at Propose a change instead.
Before you start
Permissions required
You need the Workspace Admin role to approve a change set, to apply it or to put it back. A member on any other role sees the set and every row in it, and gets the line Approving and applying need a workspace admin. beside the greyed-out Approve and Apply buttons. Marketing Ops, and any role that holds Manage on Tool Operations, can still click Reject.
Check that the tool is still connected. MarqIQ writes through the live connection, and a set cannot be applied to a tool that has been disconnected since it was proposed.
Review it
Open Tool Operations in the sidebar.
Click the tool the change set was proposed for.
Click the set under History.
A waiting set carries the amber label Waiting for approval, with the number of changes, who proposed it and the date. A set proposed by an AI assistant says (AI assistant) on that line.
Read the summary line at the top of the panel.
It states how many fields would be filled on how many people, and ends with No existing value is touched.
Read How safe it is.
It reads Fills empty fields only. It cannot replace a value, and it can be undone. for every set the product can build today.
Work down the table.
The columns are Person, Field, Now, Would become, Why and Result. Now reads empty for a fill. Why gives the reason that record was chosen, in one sentence.
Click Show all 340 to read past the first 25 rows.
The button carries your own count, and Show fewer collapses it again. Rows are sorted by the person label, so on a set near the 500 cap read a spread of rows rather than the top of the list.
Take care
You approve the whole set or you reject it. There is no control for excluding one record. If a handful of rows are wrong, click Reject, fix the cause, and have the set proposed again.
Approve or reject it
Click Approve.
The label changes to Approved, not applied yet, and your name and the date are recorded against it. Nothing has been written to your tool.
Click Reject instead when the list is wrong.
Rejecting needs the Workspace Admin role or Manage on Tool Operations, the same permission proposing needs. A rejected set can never be approved, and rejecting frees the operation so a corrected set can be proposed.
Note
A proposal more than 14 days old cannot be approved. MarqIQ labels it Expired: propose again from fresh data.
Apply it
Click Apply to HubSpot.
The button carries your tool’s name, so on Marketo it reads Apply to Marketo. It keeps that label and shows a spinner while it runs.
Wait for it to finish.
MarqIQ works through the set a batch at a time. It reads the current value of every field in the batch, writes only the items that still match what was proposed against, reads those fields again, and records what your tool answered for each record. Leave the page open, because a large set can take a few minutes.
Read the What happened line.
It counts each outcome: how many changed, how many were left as they were because they already held the value, how many were left alone because the value had changed since the proposal, how many are no longer in the tool, how many your tool refused, and how many could not be confirmed when MarqIQ read them again.
Read the Result column for anything that is not Changed.
Where your tool refused a write, its own message is printed in red under the result. Each message is also listed once above the table, under a line that names your tool such as Why HubSpot refused, with the number of changes it stopped. Copy that message when you raise it with whoever administers the tool.
| End label | What it means |
|---|---|
| Applied | Every item in the set changed. |
| Partly applied | Some items changed and some were left as they were, left alone, refused or not confirmed. This is a normal outcome, not a fault. |
| Nothing was applied | No item changed. Read the Result column to see why. The label is red when your tool refused a record, and grey when every record was left alone. |
| Not confirmed: check HubSpot (or Marketo) | No item is counted as changed, but a write your tool accepted could not be confirmed, or your tool gave no answer. Your tool may hold what MarqIQ sent, so check the records the Result column marks. Put everything back reads them again and puts back the ones that hold what MarqIQ sent. |
Note
After a successful write MarqIQ updates its own synced copy of those records to match. The next proposal for the same operation does not offer the same fills again.
Tip
Applied the wrong set? A Workspace Admin can click Put everything back. MarqIQ refuses it more than 30 days after the set was applied.
If it did not work
The Approve and Apply buttons are greyed out and a line says a workspace admin is needed
Why: You are signed in under a role other than Workspace Admin. Approving a set, applying it and putting it back are all refused by the server for every other role.
Fix: Ask a Workspace Admin to approve and apply it, or have your role changed under Team & roles.
Applying answers Approve this change set before applying it.
Why: The set is still in the proposed state. Approving and applying are two decisions, and MarqIQ will not take one for the other.
Fix: Click Approve first, then click Apply to [your tool].
The message reads Someone else has just started this. Reload to see where it stands.
Why: Two people clicked the button. MarqIQ claims a set in one statement, so it can only run once.
Fix: Reload the page and read the result. The run that claimed it is the one that counts.
The set has read Applying… for a long time and no button does anything
Why: The run was cut off part-way through the write. 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 was changed reads Changed, a record that was sent with no answer saved reads Not confirmed, and what was never sent reads Not applied yet. Put everything back is offered for the first two. For the rest the What happened line says to propose the operation again, and the same operation can then be proposed.
Nothing was written and the set went back to Approved, not applied yet
Why: Your tool would not return the current values, so MarqIQ stopped before writing anything. The message names what the tool said and ends with Nothing was changed.
Fix: Check the connection under Connected Tools, reconnect if it asks you to, then click Apply again. Nothing was changed, so there is nothing to clean up.
The message says the tool is not connected, so nothing can be written
Why: The tool was disconnected, or its saved credentials no longer work, between the proposal and the apply.
Fix: Reconnect the tool, then apply the set again. If more than 14 days have passed since it was proposed, propose it again instead.
Far fewer items changed than you approved
Why: Items whose live value moved after the proposal are skipped rather than forced, and records deleted or merged in your tool are skipped too. An item whose field already held the value is left as it was and is not counted as changed.
Fix: Read the counts on the What happened line, then see A change was skipped, refused, or only partly applied for what to do about each reason.
The message reads Too many actions in a minute.
Why: A workspace may take 30 change-set actions a minute, counting approve, reject, apply and undo together.
Fix: Wait a moment and click the button again. Nothing was changed by the refused attempt.
Next steps
Related articles
Was this article helpful?