TRIGGER: ID des Triggers oder eine voll qualifizierte Kennzeichnung.
LOCATION: Standort des Eventarc-Triggers.
Verwenden Sie die Google Cloud Console, um zu überwachen, ob Nachrichten mit dem Messwert im Pub/Sub-Thema veröffentlicht werden: topic/send_message_operation_count.
Wenn keine Nachrichten im Pub/Sub-Thema veröffentlicht werden, prüfen Sie, ob die Quelle Ereignisse generiert:
Prüfen Sie für Ereignisse aus Cloud-Audit-Logs in den Logs, ob der überwachte Dienst Logs schreibt. Wenn Logs aufgezeichnet, aber keine Ereignisse zugestellt werden, wenden Sie sich an den Support.
Prüfen Sie für Ereignisse aus Cloud Storage die Benachrichtigungen für Ihren Bucket:
gcloud storage buckets notifications list gs://BUCKET_NAME
Ersetzen Sie BUCKET_NAME durch den Namen des Buckets.
Die Ausgabe sollte in etwa so aussehen:
NOTIFICATION_CONFIG_ID: Die ID der Benachrichtigungskonfiguration.
Wenn Ereignisse zugestellt, aber keine Workflowausführungen ausgelöst werden, ist dies wahrscheinlich auf einen nicht authentifizierten Aufruf zurückzuführen. Achten Sie darauf, dass der Trigger mit einem Dienstkonto verknüpft ist, das berechtigt ist, Workflowausführungen zu erstellen. Weitere Informationen finden Sie in den Anweisungen zum Erstellen eines nutzerverwalteten Dienstkontos im Abschnitt „Erstellen eines Triggers vorbereiten“, wenn Sie einen Trigger für einen bestimmten Anbieter, Ereignistyp und Workflows-Ziel erstellen.
Wenn Nachrichten in einem Pub/Sub-Thema veröffentlicht werden, aber keine Workflowausführungen ausgelöst werden, achten Sie darauf, dass die Eventarc-Nutzlast nicht größer als 512 KB ist. Weitere Informationen zu Ressourcenlimits finden Sie unter Kontingente und Limits.
Rufen Sie in der Cloud Console die Seite Abos auf.
Wenn nicht bestätigte Nachrichten vorhanden sind, überwachen Sie die Workflowlogs für die Methode TriggerPubsubExecution.
Weitere Informationen zum Aufrufen von Workflow-Logs finden Sie unter Workflow-Logs ansehen.
Verwenden Sie den Filter Permission 'workflows.executions.create' denied, um zu prüfen, ob der Trigger einem Dienstkonto zugeordnet ist, das berechtigt ist, Workflowausführungen auszulösen. Weitere Informationen zum Zuweisen der entsprechenden Rollen für das Dienstkonto finden Sie im Abschnitt „Erstellen eines Triggers vorbereiten“, wenn Sie einen Trigger für einen bestimmten Anbieter, Ereignistyp und ein Workflows-Ziel erstellen.
Verwenden Sie das Schlüsselwort event size exceeded, um zu prüfen, ob die Ereignisgröße über 512 KB liegt.
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-08-18 (UTC)."],[[["\u003cp\u003eThis document guides you through troubleshooting common issues encountered when using Eventarc for Workflows, focusing on trigger creation failures and event delivery problems.\u003c/p\u003e\n"],["\u003cp\u003eIf trigger creation fails, ensure the target workflow exists, is active, and that the correct workflow ID and location are specified during trigger creation.\u003c/p\u003e\n"],["\u003cp\u003eIf events are not being delivered to the target, consider setting up a Pub/Sub subscription retry policy or a dead-letter topic to prevent message loss, and verify event sources.\u003c/p\u003e\n"],["\u003cp\u003eVerify that the trigger is associated with a service account that has the necessary permissions to create workflow executions if events are delivered but not triggering workflows.\u003c/p\u003e\n"],["\u003cp\u003eIf messages are published to a Pub/Sub topic but no workflow executions are being triggered, make sure the Eventarc payload is not more than 512 KB, and check for unacknowledged messages in the subscription.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot Eventarc for Workflows\n\n[Standard](/eventarc/standard/docs/overview)\n\nThis page shows you how to resolve issues that you might encounter when using\nEventarc for Workflows.\n\nFor other issues that you might also encounter, refer to troubleshooting for:\n\n- [Issues common to all destinations](/eventarc/docs/troubleshooting)\n- [Eventarc for Cloud Run](/eventarc/standard/docs/run/troubleshoot)\n- [Eventarc for GKE](/eventarc/standard/docs/gke/troubleshooting)\n\n### Trigger creation fails because workflow target does not exist\n\nYou receive an error message similar to the following: \n\n```\ncloud workflow \"projects/PROJECT_ID/locations/LOCATION/workflows/WORKFLOW_ID\" does not exist\n```\nThis output includes the following values:\n\n\u003cbr /\u003e\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: your Google Cloud project ID\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the location of your workflow\n- \u003cvar translate=\"no\"\u003eWORKFLOW_ID\u003c/var\u003e: the name of your workflow\n\nThis occurs when Eventarc is not able to find the target workflow.\nTo resolve this:\n\n1. Ensure that the target workflow exists and is ACTIVE:\n\n ```bash\n gcloud workflows list --location -\n ```\n\n \u003cbr /\u003e\n\n The output should be similar to the following: \n\n ```\n NAME STATE REVISION_ID UPDATE_TIME\n projects/PROJECT_ID/locations/LOCATION/workflows/WORKFLOW_ID ACTIVE 000004-c0c 2021-11-19T14:29:27.530185556Z\n ```\n\n \u003cbr /\u003e\n\n2. Ensure that you have provided the correct workflow ID and workflow location\n when creating the trigger.\n\n### Trigger is created successfully but target is not receiving events\n\nCheck that enough time has elapsed since creating the trigger. It can take up to\ntwo minutes before events are sent.\n\nIf the trigger still doesn't work and events are not being delivered:\n\n1. Events sent from Pub/Sub to the\n target might be getting dropped. To ensure that events aren't dropped, set up a\n [Pub/Sub subscription retry policy](/pubsub/docs/handling-failures#subscription_retry_policy)\n or [forward undelivered messages to a dead-letter topic](/pubsub/docs/handling-failures#forwarding_to)\n (also known as a *dead-letter queue*).\n\n Before setting the dead-letter topic, retrieve the trigger's topic and\n subscription: \n\n ```bash\n gcloud eventarc triggers describe TRIGGER \\\n --location=LOCATION\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eTRIGGER\u003c/var\u003e: the ID of the trigger or a fully qualified identifier.\n - \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the location of the Eventarc trigger.\n2. Use the Google Cloud console to\n [monitor](/pubsub/docs/monitoring#monitoring_forwarded_undeliverable_messages)\n if messages are published to the Pub/Sub topic with the\n metric: `topic/send_message_operation_count`.\n\n3. If messages are not being published to Pub/Sub topic, verify that\n the source is generating events:\n\n - For events from Cloud Audit Logs, check the [logs](/eventarc/docs/reference/audit-logs#viewing_logs) and make sure that the monitored service is writing logs. If logs are recorded but events are not delivered, [contact support](/eventarc/docs/getting-support).\n - For events from Cloud Storage, check notifications for your bucket:\n\n ```\n gcloud storage buckets notifications list gs://BUCKET_NAME\n ```\n Replace \u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e with the name of the bucket. \n The output should be similar to the following:\n\n \u003cbr /\u003e\n\n ```\n projects/_/buckets/BUCKET_NAME/notificationConfigs/NOTIFICATION_CONFIG_ID\n Cloud Pub/Sub topic: projects/PROJECT_ID/topics/TOPIC_ID\n Filters:\n Event Types: OBJECT_ARCHIVE\n ```\n\n This output includes the following values:\n - \u003cvar translate=\"no\"\u003eTOPIC_ID\u003c/var\u003e: the ID of the existing Pub/Sub topic.\n - \u003cvar translate=\"no\"\u003eNOTIFICATION_CONFIG_ID\u003c/var\u003e: the ID of the notification configuration.\n4. If events are being delivered but no workflow executions are being triggered,\n this is likely due to an unauthenticated invocation. Ensure that the\n trigger is associated with a service account that has permission to create\n workflow executions. For more information, follow the instructions to create\n a user-managed service account in the \"Prepare to create a trigger\" section\n when creating a trigger for a\n [specific provider, event type, and Workflows destination](/eventarc/standard/docs/event-providers-targets#triggers)\n .\n\n5. If messages are published to a Pub/Sub topic\n but no workflow executions are being triggered, make sure that the\n Eventarc payload is not more than 512 KB. For more\n information on resource limits, see [Quotas and Limits](/workflows/quotas#resource_limit).\n\n 1. In the Cloud console, go to the **Subscriptions** page.\n\n\n [Go to Subscriptions](https://console.cloud.google.com/cloudpubsub/subscription/list)\n\n \u003cbr /\u003e\n\n 2. Monitor unacknowledged messages in the subscription. For more information,\n see [Monitoring forwarded undeliverable messages](/pubsub/docs/monitoring#monitoring_forwarded_undeliverable_messages).\n\n 3. If there are unacknowledged messages, monitor the workflow logs for the\n [`TriggerPubsubExecution` method](/eventarc/docs/reference/supported-events#methodname_119).\n For more information on viewing workflow logs, see [View workflow logs](/workflows/docs/log-workflow#viewing-logs).\n\n - Use the filter `Permission 'workflows.executions.create' denied` to verify if the trigger is associated with a service account that has permission to trigger workflow executions. For more information on how to grant the appropriate roles to the service account, follow the instructions in the \"Prepare to create a trigger\" section when creating a trigger for a [specific provider, event type, and Workflows destination](/eventarc/standard/docs/event-providers-targets#triggers).\n - Use the key word `event size exceeded` to verify if the event size is over 512 KB.\n 4. If logs are recorded but events are not delivered, [contact support](/eventarc/docs/getting-support).\n\nRelated information\n-------------------\n\n- For other issues specific to Workflows, see [Troubleshoot issues](/workflows/docs/troubleshooting).\n- To get additional help, see [Get support](/eventarc/docs/getting-support)."]]
