Troubleshoot Eventarc for Cloud Run

This page shows you how to resolve issues that you might encounter when using Eventarc for Cloud Run.

For other issues that you might also encounter, refer to troubleshooting for:

Cloud Run service is not receiving events

If a service is not receiving events, the following resolutions might help:

Cloud Audit Logs events

  • Check that Admin Read, Data Read, and Data Write access is enabled for the service's audit logs.

    Go to Audit Logs

  • Check that enough time has elapsed since creating the trigger. It can take up to two minutes before the trigger is functional.
  • Follow the prerequisites for Eventarc trigger creation.
  • Check that your event filters are not too restrictive. For more information, see event filters for Cloud Audit Logs.
  • Confirm that the monitored service is generating audit logs through the Logs Explorer.

    Go to Logs Explorer

  • Check the Cloud Run logs on the Cloud Run page:

    Go to Cloud Run

    Click the service you created in Cloud Run and navigate to the Logs tab. If the logs show that the service received a non-OK status code, the Cloud Run service is rejecting events.

Pub/Sub messages

  • Confirm that the Eventarc trigger is created.
  • Confirm that the Pub/Sub topic is created and attached to the Eventarc trigger.
  • Check that the Pub/Sub topic exists: Go to Pub/Sub and search for the topic.
  • Check that enough time has elapsed since creating the trigger. It can take up to two minutes before the trigger is functional.
  • Check the Cloud Run logs on the Cloud Run page.

    Go to Cloud Run

    Click the service you created in Cloud Run and navigate to the Logs tab. If the logs show that the service received a non-OK code, the Cloud Run service is rejecting events.

Trigger is set, but target does not receive events

  • Check that the event payload you are sending does not exceed the limits on event size (512KB). The Pub/Sub push subscriptions are also subject to a set of resource limits such as throughput per publish region. This makes sure that the Pub/Sub event payload is less than 512KB.

  • Locate the Pub/Sub topic associated with the Cloud Run trigger.

    1. Go to Pub/Sub > Topics.

      Go to Topics

    2. Verify that the Pub/Sub topic name includes the name of the created trigger.

  • 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: subscription/push_request_count by response_code. If push errors are reported, check the Cloud Run 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.

Cannot find your Pub/Sub topic

The Pub/Sub topic could have been removed or modified. A new Pub/Sub topic is created when you create a trigger, so delete the existing trigger and create it again.

INVALID_ARGUMENT service does not exist error message

If you receive an INVALID_ARGUMENT: cloud run service "SERVICE_NAME" in region "REGION_NAME" does not exist error message, the service account has been deleted. Events will not be delivered to Cloud Run if the service account for the target service is deleted. Create a new Cloud Run service account.

Cloud Run service is down

Even if the Cloud Run service is down, Pub/Sub retains events for seven days by default and will retry sending events to the target. For more information on Pub/Sub resource limits, see Quotas and limits.