Gmail Trigger works normally in Test Run, but does not trigger at all after workflow is published and enabled

Help Me Build Seeking help
1

Basic Information

  • Deployment Method: Official Dify Cloud

  • Workflow Type: Workflow / Automation Workflow

  • Trigger Type: Gmail New Message Trigger (Gmail New Email / New Message Trigger)

  • UI Notification: Due to the use of this Trigger, the current workflow “does not support WebApp, Backend Service API, or MCP Service” (a relevant notice is displayed in the UI).

Issue Description

  1. In Test Run mode:

    • Using Gmail New Message as the Trigger;

    • When a new email arrives, the workflow is triggered normally and executes completely without issues;

    • This confirms that the Gmail plugin authorization, subscription, and trigger logic are all functional.

  2. After Publishing the workflow:

    • The Gmail Trigger has been explicitly set to Enabled;

    • In normal (non-test) mode, when new Gmail emails arrive:

      • The workflow shows no execution records at all (neither success nor failure);

      • No logs related to this Trigger are visible;

    • Re-entering Test Run mode allows the same Gmail new email to trigger the workflow normally again.

Confirmed Conditions with No Issues

  1. The workflow logic and Trigger configuration are correct:

    • The workflow can be reliably triggered and completed in Test Run mode.

  2. Dify Cloud-related restrictions have been ruled out:

    • Pro plan, not Sandbox;

    • Trigger Events quota not exhausted;

    • Workflow has been successfully Published.

  3. Trigger Status and Gmail Authorization:

    • After publishing, the Trigger is switched to Enabled state;

    • Gmail plugin subscription / authorization configuration is fully normal, with no errors in OAuth or subscription;

    • The Gmail account actually receives new emails.