Skip to main content
Most issues you encounter with Google have a straightforward explanation and a quick fix. This guide walks you through the most frequently reported problems — from authentication failures and API errors to slow performance and failed data imports — so you can get back to work as quickly as possible. If a problem is not covered here, visit the Support page to reach the team directly.

​
Authentication Issues

A 401 Unauthorized response means that Google was unable to authenticate your request. Check the following in order:
  1. Key validity — confirm the API key you are using is still active by visiting Settings → API and verifying the key appears in the list without a “Revoked” badge.
  2. Key expiration — if you set an expiration date when creating the key, it may have expired. Check the Expires column in the key list.
  3. Header format — your request must include an Authorization header formatted exactly as: 
    Authorization: Bearer YOUR_API_KEY
    A common mistake is sending the key without the Bearer prefix, or placing it in a different header such as X-API-Key.
  4. Environment mismatch — ensure you are not accidentally using a key from a different workspace or environment (e.g., a staging key against the production API).
If a key that was previously working has suddenly stopped, the most likely causes are:
  • The key was rotated — an Admin may have rotated the key from Settings → API. Rotation generates a new secret; the old one is immediately invalidated. Check with your workspace Admin and update your integration with the new key value.
  • The key was revoked — the key may have been deliberately or accidentally revoked. You will need to generate a new key from Settings → API → Create Key and update your integration.
  • Rate limit enforcement — if the key was used to exceed the workspace rate limit, it may have been temporarily suspended. Check the usage graph in Settings → API for a spike that correlates with when the key stopped working.
After identifying the cause, create a replacement key with the same scopes and update all applications using the old key.
If you are unable to sign in to Google, try these steps:
  1. Check your 2FA device — if your workspace requires two-factor authentication, ensure the code from your authenticator app is current (TOTP codes refresh every 30 seconds). If you have lost access to your 2FA device, click Use a recovery code on the login page.
  2. Reset your password — click Forgot password? on the login page. You will receive a reset link at your registered email address. The link is valid for 1 hour.
  3. Check your IP address — if your workspace has an IP allowlist enabled, you may be connecting from a disallowed IP. Connect from an approved network or contact your workspace Admin to update the allowlist.
  4. Clear your browser cache — stale session cookies can sometimes interfere with login. Try signing in from a private/incognito window or a different browser.
If none of the above resolves the issue, contact Google Support with your account email address.

​
API Errors

The following table covers the most common HTTP status codes returned by the Google API and what you should do when you encounter them.
Status CodeMeaningResolution
400 Bad RequestInvalid request bodyReview the API reference for required fields and correct data types. Check for missing required fields, incorrect field names, or values that do not match the expected type or format.
401 UnauthorizedMissing or invalid API keyVerify that your Authorization: Bearer <key> header is present and correctly formatted. Confirm the key is active in Settings → API.
403 ForbiddenInsufficient permissionsCheck that your API key has the necessary scopes for the action you are attempting, and that your user role grants access to the target resource.
404 Not FoundResource does not existVerify the resource ID in your request URL. The resource may have been deleted, or you may be targeting the wrong workspace endpoint.
429 Too Many RequestsRate limit exceededImplement exponential backoff and retry logic in your integration. See Rate Limits for per-plan limits and guidance on optimizing request volume.
500 Internal Server ErrorServer-side errorWait a moment and retry the request. If the error persists for more than 5 minutes, check the Google status page at status.google.com for active incidents and contact support if the issue continues.

​
Integration Issues

Slack integrations can stop working when the OAuth token used to authorize Google expires or is revoked. To fix this:
  1. Go to Settings → Integrations → Slack.
  2. Click Disconnect to remove the current connection.
  3. Click Connect to Slack and re-authorize Google with your Slack workspace.
  4. Remap your channel assignments and re-enable Slack notifications.
If re-authorizing does not resolve the issue, check whether the Google bot has been removed from the channels you mapped. Re-invite it with /invite @google inside each channel.
If your GitHub integration is not reflecting changes, the issue is usually with the webhook configuration on the GitHub side:
  1. In your GitHub repository, go to Settings → Webhooks and find the Google webhook.
  2. Check the Recent Deliveries tab for failed delivery attempts and review the error response.
  3. Confirm that the webhook URL matches the one shown in Google → Settings → Integrations → GitHub.
  4. Verify that the webhook secret in GitHub matches the secret shown in your Google integration settings.
  5. Ensure the webhook is subscribed to the correct event types (Push, Pull Request, etc.) for the sync behavior you expect.
If deliveries are succeeding on the GitHub side but records are not updating in Google, contact support with the webhook delivery ID from GitHub.

​
Data Issues

Newly created or recently updated records may not appear immediately in search results. Google’s search index is updated asynchronously — allow up to 60 seconds for new and modified records to become searchable after they are created or changed.If records are still missing after 60 seconds:
  • Confirm the records are visible when browsing the project directly (without using search).
  • Check that your search query does not include filters that would exclude the records (e.g., status filters, date ranges).
  • If you recently imported records via CSV or API bulk operations, larger batches can take up to 5 minutes to fully index.
If records are missing from both search and direct browsing, contact support.
Failed CSV imports are most commonly caused by formatting issues. Check the following:
  1. Column headers — the headers in row 1 of your CSV must exactly match the field names defined in your project schema (case-sensitive). Download the template from Project → Import → Download Template to see the expected headers.
  2. Required fields — ensure every row has a value for all required fields. Rows with missing required values are skipped and logged in the import error report.
  3. Data types — date fields must be formatted as YYYY-MM-DD, number fields must contain only numeric values (no currency symbols or commas), and boolean fields must be true or false.
  4. File encoding — save your CSV as UTF-8 to avoid issues with special characters.
  5. File size — CSVs larger than 50 MB must be split into smaller files before importing.
After correcting your file, retry the import from Project → Import → Upload CSV. A detailed error log is shown after each import attempt.

​
Performance Issues

If the Google dashboard feels slow or unresponsive, try the following steps before contacting support:
  1. Clear your browser cache — cached assets from older versions of the app can sometimes cause rendering slowdowns. Clear your cache and reload the page.
  2. Try a different browser — Google is optimized for the latest versions of Chrome, Firefox, Edge, and Safari. If you are using an unsupported browser, switching may resolve the issue.
  3. Check your network connection — run a quick speed test to rule out local network issues.
  4. Disable browser extensions — ad blockers and script-blocking extensions can interfere with app performance. Try loading Google in a private/incognito window with extensions disabled.
  5. Check the status page — if the slowness is widespread, it may indicate an active incident on Google’s infrastructure.
Always check the Google status page at status.google.com before spending time debugging — active incidents are posted there in real time, along with estimated resolution times and live updates from our team.