Klik layanan yang Anda buat di Cloud Run, lalu buka
tab Logs.
Jika log menunjukkan bahwa layanan menerima kode status non-OK, layanan Cloud Run menolak peristiwa.
Pesan Pub/Sub
Pastikan pemicu Eventarc dibuat.
Konfirmasi bahwa topik Pub/Sub dibuat dan dilampirkan ke
pemicu Eventarc.
Pastikan topik Pub/Sub ada: Buka Pub/Sub
dan cari topik.
Pastikan waktu yang cukup telah berlalu sejak pemicu dibuat.
Diperlukan waktu hingga dua menit sebelum pemicu berfungsi.
Klik layanan yang Anda buat di Cloud Run, lalu buka
tab Logs.
Jika log menunjukkan bahwa layanan menerima kode non-OK, layanan Cloud Run menolak peristiwa.
Pemicu disetel, tetapi target tidak menerima peristiwa
Pastikan payload peristiwa yang Anda kirim tidak melebihi batas ukuran peristiwa (512 KB). Langganan push Pub/Sub juga tunduk pada serangkaian batas resource seperti throughput per region publikasi. Hal ini memastikan bahwa payload peristiwa Pub/Sub berukuran kurang dari 512 KB.
Temukan topik Pub/Sub yang terkait dengan pemicu Cloud Run.
Pastikan nama topik Pub/Sub menyertakan nama pemicu yang dibuat.
Pantau
jika pesan dipublikasikan ke topik dengan metrik: topic/send_message_operation_count.
Jika pesan tidak dipublikasikan ke topik, periksa Cloud Audit Logs
dan pastikan layanan yang dipantau memancarkan log. Jika log dicatat, tetapi peristiwa tidak dikirim, hubungi dukungan.
Pantau apakah pesan
berhasil dikirim dengan metrik: subscription/push_request_count
oleh response_code. Jika error push dilaporkan, periksa log layanan Cloud Run. Jika endpoint penerima menampilkan kode status non-OK, hal ini menunjukkan bahwa kode Cloud Run tidak berfungsi seperti yang diharapkan dan Anda harus menghubungi dukungan.
Tidak dapat menemukan topik Pub/Sub Anda
Topik Pub/Sub mungkin telah dihapus atau diubah. Topik Pub/Sub baru dibuat saat Anda membuat pemicu, jadi
hapus pemicu yang ada
dan buat lagi.
Pesan error layanan INVALID_ARGUMENT tidak ada
Jika Anda menerima pesan error INVALID_ARGUMENT: cloud run service "SERVICE_NAME" in region
"REGION_NAME" does not exist, akun layanan telah dihapus. Peristiwa tidak akan dikirimkan ke Cloud Run jika akun layanan untuk layanan target dihapus. Buat
akun layanan Cloud Run baru.
Layanan Cloud Run tidak berfungsi
Meskipun layanan Cloud Run tidak berfungsi, Pub/Sub
mempertahankan peristiwa selama tujuh hari secara default dan akan mencoba lagi mengirim peristiwa ke
target. Untuk mengetahui informasi selengkapnya tentang batas resource Pub/Sub, lihat Kuota dan batas.
Informasi terkait
Untuk mempelajari Eventarc lebih lanjut, lihat ringkasan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[[["\u003cp\u003eThis document provides troubleshooting steps for issues encountered when using Eventarc for Cloud Run, covering common problems related to event delivery and service functionality.\u003c/p\u003e\n"],["\u003cp\u003eIf Cloud Run is not receiving events, check audit log access, event filter settings, trigger creation time, and confirm that the monitored service is generating audit logs or that the Pub/Sub topic exists and is properly attached.\u003c/p\u003e\n"],["\u003cp\u003eEvent delivery failures to the target may be due to exceeding event size limits (512KB) or Pub/Sub resource limits, which can be monitored through Pub/Sub metrics and audit logs.\u003c/p\u003e\n"],["\u003cp\u003eIf a \u003ccode\u003eINVALID_ARGUMENT\u003c/code\u003e error occurs indicating the Cloud Run service does not exist, the service account has likely been deleted and needs to be recreated, or if the Pub/Sub topic is missing it is suggested to delete the trigger and re-create it.\u003c/p\u003e\n"],["\u003cp\u003eEven if the Cloud Run service is down, Pub/Sub retains events and retries delivery, offering a seven-day window to resolve the service issues, but further support can be found in their contact channels.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot Eventarc for Cloud Run\n\n[Standard](/eventarc/standard/docs/overview)\n\nThis page shows you how to resolve issues that you might encounter when using\nEventarc for Cloud Run.\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 GKE](/eventarc/standard/docs/gke/troubleshooting)\n- [Eventarc for Workflows](/eventarc/standard/docs/workflows/troubleshoot)\n\nCloud Run service is not receiving events\n-----------------------------------------\n\nIf a service is not receiving events, the following resolutions might help: \n\n### Cloud Audit Logs events\n\n- Check that **Admin Read** , **Data Read** , and **Data Write** access is enabled for the service's audit logs.\n\n [Go to Audit Logs](https://console.cloud.google.com/iam-admin/audit)\n- Check that enough time has elapsed since creating the trigger. It can take up to two minutes before the trigger is functional.\n- Follow the [prerequisites](/eventarc/standard/docs/run/create-trigger-cloud-audit-logs-gcloud#before-you-begin) for Eventarc trigger creation.\n- Check that your event filters are not too restrictive. For more information, see [event filters for\n Cloud Audit Logs](/eventarc/docs/determining-filters-cal).\n- Confirm that the monitored service is generating audit logs through the **Logs Explorer** .\n\n [Go to Logs Explorer](https://console.cloud.google.com/logs/query)\n- Check the Cloud Run logs on the **Cloud Run** page:\n\n [Go to Cloud Run](https://console.cloud.google.com/run)\n 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.\n\n### Pub/Sub messages\n\n- Confirm that the Eventarc trigger is created.\n- Confirm that the Pub/Sub topic is created and attached to the Eventarc trigger.\n- Check that the Pub/Sub topic exists: Go to **Pub/Sub** and search for the topic.\n- Check that enough time has elapsed since creating the trigger. It can take up to two minutes before the trigger is functional.\n- Check the Cloud Run logs on the **Cloud Run** page.\n\n [Go to Cloud Run](https://console.cloud.google.com/run)\n 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.\n\nTrigger is set, but target does not receive events\n--------------------------------------------------\n\n- Check that the event payload you are sending does not exceed the limits on [event size\n (512KB)](/eventarc/docs/quotas). The Pub/Sub push subscriptions\n are also subject to a set of [resource limits](/pubsub/quotas#resource_limits) such\n as throughput per publish region. This makes sure that the\n Pub/Sub event payload is less than 512KB.\n\n- Locate the Pub/Sub topic associated with the Cloud Run\n trigger.\n\n 1. Go to **Pub/Sub** \\\u003e **Topics**.\n\n\n [Go to Topics](https://console.cloud.google.com/cloudpubsub/topic/list)\n\n \u003cbr /\u003e\n\n 2. Verify that the Pub/Sub topic name includes the name of the created trigger.\n\n- [Monitor](/pubsub/docs/monitoring#monitoring_forwarded_undeliverable_messages)\n if messages are published to the topic with the metric: `topic/send_message_operation_count`.\n If messages are not published to the topic, check [Cloud Audit Logs](/logging/docs/audit#viewing_audit_logs)\n and make sure the monitored service is emitting logs. If logs are recorded\n but events are not delivered, [contact support](/eventarc/docs/getting-support).\n\n- [Monitor](/pubsub/docs/monitoring#monitoring_push_subscriptions) if messages\n are pushed successfully with the metric: `subscription/push_request_count`\n by `response_code`. If push errors are reported, check the\n Cloud Run service logs. If the receiving endpoint returns a\n non-OK status code, it indicates that the Cloud Run code is\n not working as expected and you must [contact support](/eventarc/docs/getting-support).\n\nCannot find your Pub/Sub topic\n------------------------------\n\nThe Pub/Sub topic could have been removed or modified. A new\nPub/Sub topic is created when you create a trigger, so\n[delete the existing trigger](/eventarc/docs/managing-triggers#trigger-delete)\nand [create it](/eventarc/standard/docs/run/route-trigger-cloud-pubsub) again.\n\nINVALID_ARGUMENT service does not exist error message\n-----------------------------------------------------\n\nIf you receive an `INVALID_ARGUMENT: cloud run service \"SERVICE_NAME\" in region\n\"REGION_NAME\" does not exist` error message, the service account has been\ndeleted. Events will not be delivered to Cloud Run if the\nservice account for the target service is deleted. Create a new\n[Cloud Run service account](/eventarc/standard/docs/run/quickstart#event-receiver).\n\nCloud Run service is down\n-------------------------\n\nEven if the Cloud Run service is down, Pub/Sub\nretains events for seven days by default and will retry sending events to the\ntarget. For more information on Pub/Sub resource limits,\nsee [Quotas and limits](/pubsub/quotas#resource_limits).\n\nRelated information\n-------------------\n\n- To learn more about Eventarc, see the [overview](/eventarc/standard/docs/overview).\n- For a tutorial on Eventarc troubleshooting, see [Debug a Cloud Run service using Eventarc](/eventarc/standard/docs/run/debugging-events-cloud-run).\n- To get additional help, see [Get support](/eventarc/docs/getting-support)."]]
