Skip to content

Troubleshooting

This page lists the problems consultants meet most often, with the cause and the fix. For most of them, the fastest first step is to ask the agent in the session what went wrong. It reads the error, the connection and the recent runs.

The sign-in window closes without a result

Section titled “The sign-in window closes without a result”

The provider usually showed an error page. The most common cause is a redirect URI that is not registered on the provider’s sign-in app, or an app that does not allow the sign-in type.

Ask the agent to check the app. It can fix the app settings in its own browser, or it tells you the exact redirect URI to register. Then connect again.

The sign-in fails with “invalid_client”

Section titled “The sign-in fails with “invalid_client””

The client ID or the client secret is wrong, or it belongs to another app or another tenant. Ask the agent to create a new app in the provider’s admin screens with its browser, or enter the correct values in the connect card.

The agent finds fewer records than expected

Section titled “The agent finds fewer records than expected”

ERP systems and databases often filter records by user, role or company without an error. A connection then sees only part of the data.

The agent reports restricted access when the volumes do not fit together, for example when invoices refer to customers it cannot see. Ask the client’s administrator to give the connection’s user access to the missing modules or companies, then run the assessment again.

Check the secure gateway first. Run superglue-gateway check on the gateway machine, or open the gateway setup page, and follow the message. See the secure gateway troubleshooting.

The password changed, the secret expired, or the client removed the app’s access. Open the failed run under Runs and select Investigate. The agent names the cause. When the client must give access again, ask the agent to reconnect the connection.

The agent waits for your permission before it changes data in a client system. The request shows in the session, as a card in Microsoft Teams, or in an email. Select Allow to continue, or tell the agent what to change.

The agent says that superglue refused a write

Section titled “The agent says that superglue refused a write”

superglue refuses writes that nobody approved. Ask the agent to try again. It asks for the permission first.

Open the run under Runs and select Investigate. The agent explains the failure and proposes a fix. Typical causes are a changed field in the target, a new code value in the source, or an expired secret. See Post go-live.

A repaired tool runs on the next schedule. It does not repeat the failed run. Rerun the failed period manually when the sync must not skip records.

  • Failure alerts are sent for scheduled, API, webhook, CLI and tool-chain runs. Runs that you start by hand, agent runs and MCP runs send no alert. Daily and weekly summaries still count them.
  • After three failed deliveries, superglue disables the channel. Correct the channel, send a test, and enable it again.

See Notifications.

Store run results is off by default. An admin turns it on under Settings, on the Organization tab. It keeps results only for runs that start after you turn it on.

A request in a tool run stops after 60 minutes by default, and a whole run after 10 hours. Load in smaller batches, or see Limits.

  • The briefing is available on the Enterprise plan.
  • It starts when you connect your first source in Brain > Setup.
  • It arrives in Microsoft Teams when you added superglue there, otherwise by email. Check the time under Agent autonomy in Settings.

Your organization has not added the app yet. Send your Teams administrator Install superglue for your organization.

If the agent cannot solve the problem, write to support@superglue.ai. Include the session link or the run ID from the Runs page.