This article covers these error messages:
Your [Destination] connection has expired or been revoked. (invalid-credentials)
Your Google Ads connection encountered an authorization error. (invalid-credentials - Google Ads)
[Destination] authorization failed. Your access may have been revoked or permissions changed (auth-error)
Mailchimp authorization failed. Your API key may be invalid or your account may require attention. (auth-error - Mailchimp)
TL; DR
Authentication errors mean StellarAlgo can’t connect to your destination. In most cases, the account owner who originally set up the connection needs to reconnect in Profile → Preferences. If reconnecting doesn’t fix it, the issue may be on the destination’s side - check your account status there.
What This Means
When you see an authentication error, StellarAlgo tried to push data to your destination but was unable to authorize the connection. This could be because your credentials expired, your access was revoked, or the destination account itself needs attention.
There are two types of authentication errors you might see:
Your [Destination] connection has expired or been revoked - your credentials are no longer valid.
[Destination] authorization failed - the connection exists but the destination rejected the request.
Common Causes
The most common reasons for authentication errors:
Your OAuth token or API key has expired (most connections expire periodically).
Someone changed the password or revoked access on the destination side.
The destination account has been suspended, disabled, or locked (e.g., for billing or compliance reasons).
For per-user connections (Facebook, Google Ads, HubSpot, TikTok, Snapchat, Eloqua): the person who originally authorized may have left the organization or changed roles.
Steps to Resolve
In StellarAlgo, open the Profile menu in the top-right corner and select Preferences.
For the failing destination, click Reconnect.
For per-user OAuth destinations (Facebook, Google Ads, HubSpot, TikTok, Snapchat, Eloqua): the same person who originally authorized the connection should reconnect. A different user’s token may not cover the same accounts or resources.
For tenant-level destinations (Marketo, SFMC, Dynamics, Salesforce, Constant Contact): any admin can reconnect using updated credentials.
After reconnecting, re-run the failed automation to confirm the issue is resolved.
Destination-Specific Notes
Google Ads
Google Ads may show an authentication error even when your OAuth connection is fine. This can happen when your Google Ads API developer token doesn’t have the right feature-level permissions. Reconnecting won’t fix it.
If you see ‘Your Google Ads connection encountered an authorization error’:
Update the connection by visiting Profile → Preferences and click Reconnect
If the error persists after reconnecting, contact StellarAlgo support. This may require a Google Ads API access update on our side.
Mailchimp
Mailchimp returns the same error for several different problems: an invalid API key, a suspended account, a disabled account, or a GDPR-locked account. Reconnecting only fixes the first case.
If you see ‘Mailchimp authorization failed’:
Update the connection by visiting Profile → Preferences and click Reconnect
If the error persists, log into your Mailchimp account directly and check your account status. Look for any suspension notices, compliance flags, or billing issues.
If your Mailchimp account appears healthy, contact Mailchimp support for further investigation.
Still Not Working?
If reconnecting doesn’t resolve the error:
Verify the destination account is active and in good standing by logging in directly.
Check that the authorizing user still has the necessary permissions in the destination platform.
Contact StellarAlgo support with the following details: the destination name, the automation name, and the approximate time the error occurred.