This page shows you how to resolve issues that you might encounter when using Eventarc.
For destination-specific issues that you might also encounter, refer to troubleshooting for:
This section provides troubleshooting tips for issues at the source of events (the provider).
Provider doesn't exist
Events are produced from the provider, but are not received at the target
Check that you are filtering for events from providers that are in a supported region for the target destination. For more information, see locations supported by Eventarc and Understand Eventarc locations.
Trigger is not delivering events
Verify that a Pub/Sub topic with the same trigger name exists.
To list triggers in all locations, run:
gcloud eventarc triggers list --location=-
To list Pub/Sub topics, run:
gcloud pubsub topics list
Verify that the Pub/Sub topic name includes the name of the created trigger. If the Pub/Sub topic is missing, create a topic when you create the trigger.
To describe triggers and detect any issues with the condition of the trigger, run:
gcloud eventarc triggers describe TRIGGER \ --location=LOCATION
Replace the following:
TRIGGER: the ID of the trigger or a fully qualified identifier.
LOCATION: the location of the Eventarc trigger.
The previous command returns the condition of the trigger. If there is an issue with the Pub/Sub topic, one of the following conditions is returned:
conditions: transport.pubsub.topic: code: NOT_FOUND message: Pub/Sub topic not found. Try recreating the trigger.
conditions: transport.pubsub.topic: code: UNKNOWN message: Pub/Sub topic status is unknown. Try requesting the trigger description again.
If applicable, do the following:
Pub/Sub topic not foundis returned, recreate the trigger and create the topic:
Pub/Sub topic status is unknownis returned, run the command to describe the trigger again.
Verify the health of the Pub/Sub topic:
Verify the Cloud Pub/Sub topic configuration.
Monitor if messages are published to the topic with the metric:
topic/send_message_operation_count. If messages are not published to the topic, check Cloud Audit Logs and make sure the monitored service is emitting logs. If logs are recorded but events are not delivered, contact support.
Monitor if messages are pushed successfully with the metric:
response_code. If push errors are reported, check the service logs. If the receiving endpoint returns a non-OK status code, it indicates that the Cloud Run code is not working as expected and you must contact support.
This section provides troubleshooting tips for issues at the trigger.
Permission denied errors
If you encounter a
Failed to load service details: permission deniederror, confirm that the trigger permissions are configured correctly, and that the Pub/Sub service account is granted the
iam.serviceAccountTokenCreatorrole. For more information, see Access control.
If you encounter the following error while trying to create a trigger, wait a few minutes (up to seven), and then try creating the trigger again:
Permission denied while using the Eventarc Service Agent. If you recently started to use Eventarc, it may take a few minutes before all necessary permissions are propagated to the Service Agent. Otherwise, verify that it has Eventarc Service Agent role.
A service agent is a Google-managed service account that acts as the identity of a given Google Cloud service for a particular project. For more information, see Service agents and view the permissions for the Eventarc service agent role (
To verify that the Eventarc service agent exists in your Google Cloud project and has the necessary role, complete the following steps:
In the Google Cloud console, go to the IAM page.
On the Permissions tab, select the Include Google-provided role grants checkbox.
In the list of principals, locate the Eventarc service agent, which uses this format:
Verify that the service agent has the Eventarc Service Agent role. If the service agent does not have the role, grant the role.
Unexpected charges when using Eventarc
When you create a trigger, check if the filters configured could lead to triggers being set off indefinitely. To help avoid unexpected charges on your bill, set budgets and alerts using Google Cloud's billing console. For more information, see Create a budget.
- To learn more about Eventarc, see the overview.
- For a tutorial on Eventarc troubleshooting, see Debug a Cloud Run service using Eventarc.
- For event publishing issues, see Troubleshoot event publishing.
- To get additional help, see Get support.