Linking to GitHub FAQ
This article lists frequently asked questions about linking to GitHub from the Tealium platform.
Frequently Asked Questions
I am getting a message that says my authorization is invalid, what can I do?
This can be caused when automatic or manual syncing fails due to one of the following reasons:
- GitHub is down.
- The URL being used to retrieve the file no longer is valid. For example, the file was renamed or deleted on GitHub.
- There are too many snippets trying to be synced (more than 10).
- The personal access token was revoked or the GitHub account was deleted.
How can I correct invalid authorization errors?
- If GitHub is down, there is nothing you can do until the service is up again. You can keep using the extension as normal but will not be able to get the latest code from GitHub. If this is the case, a message with a timestamp will display that the system is unable to connect until GitHub is back up.
- If the URL being used to retrieve the file is no longer valid, you can delete the snippet if it is no longer needed and replace it with a new snippet containing the new URL.
- If you have more than 10 GitHub snippets that were configured to automatically sync, delete the extra snippets if possible.
- If the credentials are invalid, contact your GitHub account manager or contact GitHub support. In some cases, support may might need to unlink your account and relink it with a new access token.
What happens to referenced files in my configuration if I unlink my GitHub account?
- If you unlink your GitHub account, the referenced files remain unchanged in your configuration, but are now disconnected from the GitHub repository and can no longer be synchronized.
- If the account is unlinked, then linked again, the referenced files reconnect to the repository and can be synchronized again.
This page was last updated: January 30, 2023