Clique no serviço criado no Cloud Run e navegue
até a guia Registros.
Se os registros mostrarem que o serviço recebeu um código de status diferente de OK, o serviço Cloud Run rejeitará eventos.
Mensagens de Pub/Sub
Confirme se o gatilho do Eventarc foi criado.
Confirme se o tópico do Pub/Sub foi criado e anexado ao gatilho do Eventarc.
Verifique se o tópico do Pub/Sub existe: acesse Pub/Sub e pesquise o tópico.
Verifique se já passou tempo suficiente desde a criação do gatilho.
Pode levar até dois minutos para o gatilho começar a funcionar.
Verifique os registros do Cloud Run na página
Cloud Run.
Clique no serviço criado no Cloud Run e navegue
até a guia Registros.
Se os registros mostrarem que o serviço recebeu um código de status diferente de OK, o serviço Cloud Run rejeitará eventos.
O gatilho está definido, mas o destino não recebe eventos
Verifique se o payload do evento que você está enviando não excede os limites de tamanho do evento
(512 KB). As assinaturas de push do Pub/Sub também estão sujeitas a um conjunto de limites de recursos, como a capacidade por região de publicação. Isso garante que o payload de evento do Pub/Sub seja inferior a 512 KB.
Localize o tópico do Pub/Sub associado ao gatilho do Cloud Run.
Verifique se o nome do tópico do Pub/Sub inclui o nome do gatilho criado.
Monitore se as mensagens forem publicadas no tópico com a métrica: topic/send_message_operation_count.
Se as mensagens não forem publicadas no tópico, verifique os Registros de auditoria do Cloud e verifique se o serviço monitorado está emitindo registros. Se os registros forem gravados, mas os eventos não forem entregues, entre em contato com o suporte.
Monitore se as mensagens
forem enviadas com a métrica: subscription/push_request_count
por response_code. Se erros de push forem relatados, verifique os
registros de serviço do Cloud Run. Se o endpoint de recebimento retornar um
código de status não OK, isso indicará que o código do Cloud Run não está funcionando como
esperado e você precisa entrar em contato com o suporte.
Não foi possível encontrar seu tópico do Pub/Sub
O tópico do Pub/Sub pode ter sido removido ou modificado. Ao criar
um gatilho, um novo tópico do Pub/Sub é gerado. Portanto,
exclua o gatilho existente e
crie-o novamente.
A mensagem de erro: serviço INVALID_ARGUMENT não existe.
Se você receber uma mensagem de erro INVALID_ARGUMENT: cloud run service "SERVICE_NAME" in region
"REGION_NAME" does not exist, a conta de serviço foi excluída. Os eventos não serão entregues ao Cloud Run se a conta de serviço
do serviço de destino for excluída. Crie uma nova conta de serviço do Cloud Run.
O serviço do Cloud Run está inativo
Mesmo que o serviço do Cloud Run esteja inativo, o Pub/Sub mantém eventos por sete dias por padrão e tentará repetir o envio de eventos para o
destino. Para mais informações sobre limites de recursos do Pub/Sub, consulte Cotas e limites.
Informações relacionadas
Para saber mais sobre o Eventarc, consulte a visão geral.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-02 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)."]]
