Change sets are not available in my new workspace
A brand-new workspace, and a workspace for a few hours after a release that adds a table, can open Tool Operations and be told change sets are being set up. That message is a wait, not a fault, and nothing is needed from you. This article tells you how long, and how to tell it apart from the three other reasons the panel can refuse — a plan, a permission, and a tool change sets do not cover. To understand what a change set does once it is available, read How a change set works: propose, approve, apply, undo.
Before you start
Open Tool Operations in the left-hand menu, choose your tool and scroll to Changes MarqIQ can make for you. Read the exact sentence on screen. Each of the four below says something different, and they have different answers.
Which of the four messages you have
| What it says | Where it sits | What it means |
|---|---|---|
| Change sets are being set up for this workspace… | The red strip under the heading | A wait. Your workspace database does not have the two tables yet. This article |
| Change sets is part of the Pro plan — your workspace is on … | The red strip under the heading | A plan. Starter does not include Tool Operations |
| Approving and applying need a workspace admin. | Grey text beside a change set in History | A role. Approving a set, applying it and putting it back are refused by the server for anyone who is not a Workspace Admin |
| Change sets work in HubSpot and Marketo today. There is none for <tool> yet. | A plain card where the operations would be | The tool. Not a wait, and it will not change by waiting |
Note
The setting-up message is the only one of the four that clears on its own.
Why a new workspace waits at all
Every workspace has its own database. That is what keeps one customer’s records out of another’s, and it is also why a table cannot appear everywhere at once.
- A workspace database is created the first time something writes for that workspace, never on a schedule. A workspace nobody has used yet has no database, by design.
- It gets the whole schema at that moment, and nothing after it. A release deploys its schema to MarqIQ’s control database only.
- So a table added by a later release has to be created in each existing workspace database one at a time, by a maintenance job that runs inside MarqIQ.
- Change sets need two such tables. Until yours has them, MarqIQ answers with one plain sentence rather than an error page.
How long it takes
- The table-and-index maintenance runs once an hour, on the hour. The three shorter runs at quarter past, half past and quarter to exist to move syncs already in motion, and deliberately skip this work.
- Each hourly run brings up to four workspace databases up to date. How long your workspace waits therefore depends on how many are behind, which is why the message says a few hours rather than a time.
- A workspace whose database could not be reached is rested for six hours and sent to the back of the queue, so a healthy workspace is never stuck behind an abandoned one.
- A workspace whose database creation failed or stalled is a separate queue: one is retried on every run, four times an hour, oldest attempt first.
- Nothing is queued on your side. There is no job of yours waiting, and re-opening the page does not move you up.
Take care
Do not read this as your sync being broken. Syncing, the analyses and the reports all read your workspace database and carry on normally throughout. It is only the two change-set tables that are missing.
What to do in the meantime
Everything needed before a first change set is worth doing now, and none of it is blocked.
Map your first-touch fields under Tool Operations › Field Mapping.
MarqIQ does not check your mapping before it proposes. Where a field is not mapped, MarqIQ proposes against its own default name — utm_source, utm_medium and the rest — so unless your tool holds properties with exactly those names, the first run goes wrong after the wait instead of being refused during it.
Run a sync for the tool from Data sources.
A proposal is built from MarqIQ’s synced copy of your records, so a fresh sync means a fresh list.
Open the Analysis screen and read the findings.
Nothing there writes to your tool, and it is where the records a change set would fix are named.
Agree inside your team who approves.
Applying and putting a set back are refused by MarqIQ for anyone who is not a Workspace Admin, so decide now who that is.
An unmapped field is never refused
Neither operation stops for a missing mapping, and the two go wrong in different ways. Fill empty first-touch fields from what MarqIQ captured takes its new values from MarqIQ’s own record of the first visit. It reads MarqIQ’s default property as empty in your tool, because no property of that name is there, so a full change set is built and an admin can approve it. Applying it is where it breaks: your tool refuses a property it does not have, and MarqIQ either marks every item failed with the tool’s own message, or stops before writing anything and ends “Nothing was changed.” Fill empty first-touch fields from the most recent touch reads both sides under the default names, finds both of them empty, and skips every person. That answers “Nothing to change: no person in <tool> has an empty first-touch field that this could fill. That is the good outcome.” — word for word what a tool with nothing left to fill says. Read either answer as a mapping to check.
The messages, one by one
Change sets are being set up for this workspace. MarqIQ prepares each workspace in turn, on the hour, so this can take a few hours after a release. Nothing is needed from you.
Why: Your workspace database does not carry the two change-set tables yet. Either the workspace is new, or a release added a table and the hourly maintenance has not reached you.
Fix: Come back later the same day. Nothing is lost and nothing is queued. Where it is still there after a full day, send support your workspace name — that is long enough for it to be a fault rather than a queue.
Change sets is part of the Pro plan — your workspace is on Starter. See Account settings › Subscription to upgrade.
Why: Tool Operations is not in the Starter plan. This is a plan boundary, not a wait.
Fix: Upgrade the workspace, or use a Free Trial, Pro, Business, Enterprise or Partner workspace. The message names the plan that unlocks it and the plan you are on.
Change sets work in HubSpot and Marketo today. There is none for your tool yet.
Why: Change sets are built for HubSpot and Marketo. No other connected tool has one.
Fix: Nothing to wait for. Read the analyses for that tool and make the change in the tool itself.
The panel loads but both buttons are greyed out
Why: The tool is not connected. The buttons are disabled until it is.
Fix: Open Connected Tools, reconnect the tool and come back. A proposal is also refused with “<tool> is not connected” from the server, so you will see it either way.
Approving and applying need a workspace admin.
Why: You are signed in under a role other than Workspace Admin, so the Approve and Apply buttons are greyed out for you. Proposing a change and rejecting one need Manage on Tool Operations, which Workspace Admin and Marketing Ops hold. Approving a set, applying it and putting it back are refused by the server for anyone who is not a Workspace Admin.
Fix: Propose the set, where your role lets you, and ask a Workspace Admin to approve and apply it. A proposal writes nothing to your tool until a Workspace Admin approves and applies it, so it is safe to leave waiting. Who can approve what lists who may take each step.
20 change sets are already open in this workspace, the most that can be open at once.
Why: A workspace may hold 20 open change sets at once. A record an open set lists is never proposed twice, so there is no need for more to wait.
Fix: Open History, and approve or reject some of the waiting sets, or apply the approved ones, before proposing another.
This workspace has proposed 20 change sets in the last minute, the most it may in one.
Why: A workspace may make 20 proposals a minute, and 30 approve, reject, apply or undo actions a minute.
Fix: Wait a minute and try again. Nothing was saved and nothing was written.
If it did not work
One workspace has change sets and another does not, on the same plan
Why: Each workspace database is brought up to date separately, a few per hour. Two workspaces created on the same day can be days apart in that queue.
Fix: Use the one that works meanwhile. The other clears without anybody doing anything.
The message appeared on a workspace that had change sets last week
Why: A release added a new table, and the maintenance has not reached your workspace yet. The same wait applies to an existing workspace as to a new one.
Fix: Come back later the same day. Any change set already applied is unaffected: it lives in your workspace database and its history is intact.
You are not sure whether it is a wait or a fault
Why: Two of the four share the same red strip, and only one of them is a wait.
Fix: Match the exact wording against the table above. The setting-up message names no plan, no role and no tool, and ends “Nothing is needed from you”. The other three all name one of those three things.
You want to know when it clears
Why: MarqIQ sends no notification when a workspace database is brought up to date.
Fix: Re-open the page later in the day. The panel loads the operations as soon as the tables exist, with no further setup.
Next steps
Related articles
Was this article helpful?