---
title: Gmail (Legacy) troubleshooting
slug: gmail-legacy-troubleshooting
image: https://make-cxp-documentation.ams3.cdn.digitaloceanspaces.com/apps-center-icons/PREVIEW_DEFAULT.png
docTags: 
createdAt: 2025-03-12T12:02:00.904Z
---

Explore the following error codes to help you build your scenarios with Gmail modules.

# Error 400: Failed to Verify a Connection

Your connection has expired and is no longer valid. You need to reauthorize the connection every seven days.

This error affects non-Google Workspace accounts. For more details, please refer to [Google OAuth documentation](https://developers.google.com/identity/protocols/oauth2#expiration).

Due to Google's updated security policy, unpublished apps can only have a 7-day authorization period. After the OAuth security token expires, the connection is no longer authorized and any module relying on it will fail.

## Solution

### Option 1

**To avoid weekly reauthorization**, you can update the publishing status of your project.

If you update your project to the **In production** status, you will not be required to reauthorize the connection weekly.

Change the status of your project by following these steps:

::::WorkflowBlock
:::WorkflowBlockItem
Log in to the [Google Cloud Platform](https://console.cloud.google.com/) using your Google credentials.
:::

:::WorkflowBlockItem
Navigate to the **Oauth consent screen**.
:::

:::WorkflowBlockItem
Click the **Publish app** button next to your app.
:::

:::WorkflowBlockItem
If the **Needs verification** message appears, choose whether to go through the [Google verification process](https://support.google.com/cloud/answer/13463073?visit_id=638357423877979226-2405331664\&rd=1#exceptions-ver-reqts) for the app or to connect to your unverified app. Currently connecting to unverified apps works in Make, but we cannot guarantee the Google will allow connections to unverified apps for an indefinite period.
:::
::::

For more information regarding publishing statuses, refer to the **Publishing status** section of [Google's Setting up your OAuth consent screen help](https://support.google.com/cloud/answer/10311615#zippy=) and our [Community page](https://community.make.com/t/gmail-google-drive-verification-issues-error-400-how-to-solve/27432).

### Option 2

If you keep your project in the **Testing** status, you will be required to reauthorize your connection in Make every week.

Reauthorize your Google connection by following these steps:

::::WorkflowBlock
:::WorkflowBlockItem
Log in to Make.
:::

:::WorkflowBlockItem
Go to **Connections**.
:::

:::WorkflowBlockItem
Find your Google connection and click the **Reauthorize** button.
:::
::::

# Error 403: Access Denied

You didn't add a test user for your project in Google Cloud Platform, and the project has the **Testing** status. You need to add the email address associated with the Google account you want to connect with Make as a Test user.

::::WorkflowBlock
:::WorkflowBlockItem
Log in to the [Google Cloud Platform](https://console.cloud.google.com/) using your Google credentials.
:::

:::WorkflowBlockItem
Go to **APIs & Services** > **OAuth consent screen**.
:::

:::WorkflowBlockItem
Under **Test users**, **+ Add Users** and enter an email of a user that you want to create a connection for.
:::

:::WorkflowBlockItem
Click **Save**.
:::
::::

# Error 403: Access Not Configured

The **Gmail API** was disabled in the Google Cloud Platform. You need to [enable it](docId\:v6l8KMmwflB2wxhoi3TRp) again.