Skip to main content
Mist can look inside a connected back-office integration and help you fix it. Ask in plain words, such as “Why didn’t order 10482 sync to Exigo?” or “What’s failing in our Exigo sync?”. Mist runs the integration’s actions for you: checks that only read, and fixes that change records. A fix never runs until you approve its plan. Today this works for Exigo. Mist works only on the company you’re signed in to.

​
Before you start

  • Your company has the Exigo connector installed and connected. See Back-office connectors.
  • You’re signed in to Mist as an admin of the company. Mist acts as you, and it can’t use a company API, partner or droplet token for this.
  • Your role has the Integration Ops permissions you need. On the Roles screen, Integration Ops is in the Settings card. Open it to switch each permission on or off:
Each action has a tier: view, run or run_guarded. You need the permission for an action’s tier to preview or apply it. An action that changes records always needs at least Run standard integration ops actions to apply, whatever its tier.

​
Ask Mist what’s failing

Mist works from the safest check to the riskiest change:
  1. It lists what’s failing, grouped by cause, with how many different records each group affects. See What failure groups mean.
  2. It checks one record from a group to find out what happened to it.
  3. Depending on what it finds, it tests the connection, checks the connector’s webhooks, or checks your mappings.
  4. Only when the cause is fixed does it offer to retry the records that failed.
Checks that only read are their own answer. Mist shows you the result and every warning, and there’s nothing to approve. What Mist can check, all with the view tier:
  • What’s failing, grouped by cause. Groups whose source data needs fixing are counted separately, because a retry won’t help them.
  • What happened to one record.
  • Whether Fluid can reach and sign in to Exigo. A passing test doesn’t guarantee that every sync works.
  • Whether the connector’s webhook subscriptions are all there and active.
  • Whether your mappings have gaps, blank matches, or values that differ only by case or spaces.
  • The products reconciliation. Mist reads the last saved check and never runs a new one. If there’s no recent check, open Reconciliation on the connector’s screen and click Check now, then ask again. See Check reconciliation.
Fixes Mist can plan include retrying failed records (run) and registering missing webhooks or turning inactive ones back on (run_guarded). Mist reads the full list of actions from your integration, with each action’s tier, before it uses one. A retry follows the same rules as a replay on the connector’s screen. See Which records you can replay.

​
Approve a fix

When a fix would change records, Mist first previews it. The preview changes nothing in your integration, but it’s recorded in the history.
1

Read the plan

Mist tells you what the fix will do: how many records, which ones, and any warnings, such as changes that can’t be undone. Read every warning.
2

Approve or decline

An approval card appears in the chat. Click Approve to run exactly that plan, or Decline to stop. The card then reads Approved or Declined.
3

Check the result

Mist runs the fix and follows it until it finishes. A fix ends as succeeded, partly succeeded, failed or cancelled. Mist tells you which.
An approval covers one plan, once, for 15 minutes. If the plan changes, or the connector’s settings change before the fix runs, Mist previews again and asks you again. To stop a fix that’s still waiting or running, ask Mist to cancel it. A fix that’s waiting stops at once. A running fix stops as soon as it can. A finished fix can’t be cancelled. If an action has an undo action, Mist tells you its name. Mist doesn’t run it for you.

​
When Mist stops

Mist doesn’t retry on its own. It stops and tells you what it checked when: Mist also stops when a retry fails again for the same reason, when the cause is on your back office’s side, such as credentials or data only you can correct, or when a plan affects far more records than you expected. If you need help with a fix Mist can’t make:
Email Fluid support at help@fluid.app. The Getting help page lists what to include in your request.

​
See what Mist did

Ask Mist for the integration’s history. It lists every preview and every fix applied, by anyone at your company.