Reconnecting after a permission change
An integration that was working and then silently stopped is most often caused by a permission change on the other side.
An integration that was working stopped, without you having disconnected it yourself.
Most common cause: permission changed on the other side
The connected Google or Slack account's access can be reduced or revoked entirely without any change happening in Vyera, for example when an admin updates who can access a property or which apps are authorised. Check the integration's status in Integrations, then reconnect using an account that still has the access it needs.
Other causes, by how often they happen
Note
These are ordered by frequency. Work through them in order rather than jumping to the last one.
- The Google or Slack account itself was deactivated or removed from your organisation.
- An organisation-wide policy change restricted third-party app access after the integration was first connected.
This versus a first-connection failure
This covers an integration that worked before and then broke. If you are trying to connect Google for the first time and it is failing, see Fixing a failed Google connection instead.
If none of this fixes it
Send the integration and roughly when it stopped working using the request option below.
Was this useful?
Related articles
- Disconnecting an integration safely
Disconnecting stops new data immediately, but what you have already collected is not deleted with it.
- Fixing a failed Google connection
Most failed Google connections come down to account access. Check that first, then try reconnecting.
- What data each integration sends and receives
Slack only receives posts from Vyera; Search Console and GA4 only send your own data to Vyera.
Still stuck?
Send this to the team and we will pick it up.