Skip to content

Troubleshooting Authorization Errors

When you take an action like running a report, Amalgam connects to your linked accounts to pull in the latest data. Occasionally, something on the other end prevents us from accessing that data, and you’ll see an authorization error.

The most common cause for this is a broken integration, so when this happens Amalgam will prompt you to refresh the connection. But this doesn’t necessarily mean your integration is broken. In some cases your connection is working just fine — the issue is more specific than that.

If you’ve already tried refreshing your connection

Section titled “If you’ve already tried refreshing your connection”

If you clicked “Refresh Connection” and are still seeing this error, that’s actually useful information. It tells us the issue isn’t with your connection itself — it’s something else on the connected platform’s side that’s preventing access to the data your report needs.

Here are the most likely causes and what you can do about them:

The account permissions have changed. If someone on your team recently updated roles or permissions in the connected platform, Amalgam may no longer have access to the data it needs. This can happen after an admin change, a security review, or an update to your subscription plan. Check your account settings on the connected platform and make sure the account Amalgam is connected through still has access to the relevant data.

Certain data types are restricted. Some platforms limit access to specific kinds of data depending on your plan level or how the integration was originally set up. You may be able to run most reports without issue, but hit a wall when a report tries to pull from a restricted area. Check whether your plan on the connected platform has changed, or whether the data you’re reporting on requires an upgraded tier.

The connected platform is experiencing a temporary issue. Occasionally, the problem is on the other service’s end entirely. If everything on your side looks correct, try running the report again in a few minutes.

The simplest fix is often just to refresh your connection. If Amalgam is giving you the option to reconnect, go ahead and try it — this resolves the majority of authorization issues. If the error comes back after reconnecting, the causes listed above are the next place to look.

If you’ve tried the steps above and the issue persists, we’re here to help. Reach out to our support team and include the following so we can get to the bottom of it quickly:

  • Which report you were trying to run
  • Which integration is involved (e.g., QuickBooks, Xero)
  • Whether the error happens every time or only occasionally
  • Any recent changes to your account or team permissions on the connected platform

You can contact us at [emailprotected] or through the help menu in the app. We’ll take a look and get you back on track.