Almost always this, in order:

It's hidden for their security group, and a fully up-to-date Minuet will still hide it. In the Minuet Admin Console: Setup → Security Groups → select the group → expand Setup → System Settings → API → enable FirstIgnite Auto Connect. The settings then appear under Setup → System Settings → Third Party Services → FirstIgnite.

The Admin Console is a separate application, not a page in the Minuet web app, so there's no point hunting for it in the browser. Institutions usually run it as a published remote application that opens like an ordinary program on the desktop. Inteum support can set an administrator up with it.

If System Settings itself isn't there, they don't have Minuet administrator rights. If the FirstIgnite option still doesn't appear, your Minuet licence may not include API access. Inteum support can confirm.

This section only applies if you connected with the older, credential-based setup wizard, which is for Minuet instances older than version 20 (Minuet 19 at minimum). On Minuet 20 or later, reconnect from Minuet instead. See Connecting FirstIgnite to your Minuet instance.

Authentication failed means Minuet rejected the credentials. Check, in order:

Credentials expire 60 minutes after they're generated. If setup ran long, regenerate and paste the new pair.

Connection failed means FirstIgnite couldn't reach Minuet. Confirm the base URL and that Minuet answers on 443 from outside your network.

Granting an endpoint and being allowed to read the data are two different things. This is the most common cause of a healthy-looking connection that returns nothing.

Granting an endpoint allows the call. What the call returns is decided by the Minuet user the API client runs as. FirstIgnite's connection test checks the first and not the second: it reads Minuet's list of accessible endpoints and compares it against what it needs, without calling them. So a passing test doesn't prove that the account can read a particular record or file.

So a connection can report everything verified and still return nothing, because the account behind the client can't see those records. Symptoms include an empty technology list, or contacts and companies never matching.

Start with Technology → Financials. FirstIgnite asks for the technology's Net Revenue column on every portfolio load. If the Minuet user can't read that column, Minuet rejects the whole request and the technology list comes back empty, not partially but entirely. That has been the cause every time we've seen it, and one institution's list was empty for three days before anyone checked it.

If contacts or companies are the problem rather than technologies, have them check that user's permissions on those records instead.

Once the permission is granted, reload. FirstIgnite caches list results for about a minute. If Minuet refused a remarks lookup, that refusal can stay cached for up to 15 minutes after the permission changes, so remarks and remark attachments may take that long to come back. If a field has only just been added in Minuet, the field list itself is cached for 24 hours, and an admin can force it with Refresh from Minuet under Additional Fields visibility.

The required endpoint set grows as FirstIgnite ships features, so a connection set up a while ago falls behind. When that happens, the feature that needs the new endpoint says so, and Minuet shows "Required endpoints out of date" in FirstIgnite's system settings.

A Minuet administrator can fix it in about a minute:

Then reload the FirstIgnite page in Minuet's system settings, check that the notice has cleared, and try the feature again. You can also re-test the connection in FirstIgnite under Minuet Settings, but you don't have to. For the same steps with screenshots, see Enable new FirstIgnite endpoints in Minuet.

If your Minuet instance accepts public connections, your IT team can request the path below from outside your network. If your firewall only allows FirstIgnite's IP addresses, contact FirstIgnite support so we can check the connection from our US or EU environment.

/<minuet-path>/MinuetIdentity/idsrv/.well-known/openid-configuration

A 200 means the path is open. A connection that drops instantly means the traffic isn't reaching Minuet. A 401 on an /api/… path is a healthy sign. The endpoint is alive and asking for authentication.

Below Minuet 20.0203, the API doesn't accept recipient rows, so FirstIgnite writes them into the body of the remark. Nothing is lost. Upgrading restores the structured Recipients tab.

Check the Log to panel before sending. Two things prevent it, and neither stops the email:

FirstIgnite caches your Minuet version for up to 24 hours, so a version-gated feature can lag a day behind the upgrade. For example, files attached to remarks, emails and activities appear in the document picker from Minuet 20.1010, but may take up to a day to show after you upgrade. Test Connection doesn't clear this cache.

Those values come from the managed lists in your own Minuet instance. If nobody has populated the Marketing Target Status list there, the dropdown has nothing to show. It's a Minuet configuration step.

Priority is a different case. In Minuet that list is shared with financials, activities and invoicing, so it will always contain entries irrelevant to marketing. That's expected.

An old record stored in a legacy format the API can't return cleanly. It's intact. Open it in Minuet.

Correct and unavoidable. The Minuet API doesn't return remarks flagged to be excluded from reports at all, so FirstIgnite never receives them.

Your Minuet connection doesn't have the Disclosure endpoint (POST /api/disclosures) yet. Most sites connected before the document picker was expanded won't have it. The notice offers Open Minuet system settings, Learn more and Check again. Open Minuet system settings takes you to Minuet, where an administrator enables the endpoint.

A Minuet administrator enables it once, using the steps in "A feature reports missing permissions after it used to work" above. After that, select Check again. The Disclosure tab can then list disclosure files the connected Minuet account can read.

Check where the file is attached in Minuet, then look in the matching place in the document picker:

Minuet didn't answer in time, so FirstIgnite couldn't tell whether those records already existed. It leaves them out rather than risk duplicates. Minuet's API has no delete, so a duplicate is permanent.

Run the send again, or tick individual rows to send them anyway if you're confident they're new.

If the same rows come back unchecked a second time, it isn't a slow response. Check the API user's permissions on contacts and companies, as above. A record-level refusal surfaces here as an unchecked row.