Connector errors

Invalid tokens, wrong domains, and connectors that stopped working.

"The token is invalid"

Almost always one of four things:

1. It was mistyped or truncated. Long secrets frequently lose characters on copy. Re-copy the whole value.
2. It lacks permission. Inverity needs to read and add assets. A read-only token connects but can never write back. Re-create it with write access.
3. It expired. Some platforms issue tokens with an expiry date. This is the usual cause when a connector worked for months and then stopped.
4. It belongs to a different project, space, or account than the one you're trying to connect.

Re-create the token in your platform, then paste it again under Connectors. See Tokens and permissions.

"Domain not found"

For domain-based DAMs — Bynder, Acquia DAM, Canto, Frontify — the domain or portal URL must be exactly as it appears in your platform, including the subdomain. Compare it character by character against your browser's address bar.

Nothing is being optimized after I connected

The connection succeeded; the scope is empty. Confirm:

• You selected folders or collections to watch. Connecting alone doesn't start anything.
• Those locations contain supported image or video files — see Supported formats.
• You're looking at the right space, dataset, environment, or store. Many platforms have several, and optimizing a staging environment doesn't change production.

New media in a watched location is optimized going forward. To process assets that were already there, run optimization on the folder from the dashboard. See Choose what to optimize.

It worked, then stopped

In order of likelihood:

1. You reached your monthly volume. Check Settings → Plan. See Volume and usage.
2. The token expired, or was revoked in your platform.
3. The person who authorized it lost access. If the connector was authorized under an individual's account rather than a service account, revoking their platform access breaks the connector. See Team and roles.
4. There's an active incident. Check Status and incidents.

The OAuth sign-in fails or loops

You may not have permission to install integrations on that account. Ask whoever administers the platform to run the authorization — OAuth can't be delegated with a pasted credential the way a token can.

I connected the wrong space or store

Remove the connector and connect again with the right one. Nothing you optimized in the wrong place is damaged — those assets were optimized correctly, just somewhere you didn't intend.

Platform-specific issues

Each setup guide has a troubleshooting section for its own platform — see CMS connectors and DAM connectors.