[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-08-18 (世界標準時間)。"],[[["\u003cp\u003eI/O metric charts utilize canonical error codes, and if these codes persist, this document provides potential causes and actions to resolve them.\u003c/p\u003e\n"],["\u003cp\u003eErrors such as \u003ccode\u003eRESOURCE_EXHAUSTED\u003c/code\u003e may indicate that the project has exceeded its resource quota or API rate limiting quota, which requires adjusting the quota.\u003c/p\u003e\n"],["\u003cp\u003eIssues like \u003ccode\u003eDEADLINE_EXCEEDED\u003c/code\u003e, \u003ccode\u003eINVALID_ARGUMENT\u003c/code\u003e, \u003ccode\u003eFAILED_PRECONDITION\u003c/code\u003e, and \u003ccode\u003eOUT_OF_RANGE\u003c/code\u003e typically involve checking the source/sink configuration, worker logs, or resource existence.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eUNAUTHENTICATED\u003c/code\u003e and \u003ccode\u003ePERMISSION_DENIED\u003c/code\u003e errors suggest that the Dataflow service account lacks necessary Identity and Access Management permissions or the relevant APIs aren't enabled.\u003c/p\u003e\n"],["\u003cp\u003eErrors like \u003ccode\u003eUNKNOWN\u003c/code\u003e, \u003ccode\u003eINTERNAL\u003c/code\u003e, or \u003ccode\u003eUNAVAILABLE\u003c/code\u003e suggest the service might be down, and users should check the Cloud Status Dashboard for updates.\u003c/p\u003e\n"]]],[],null,["The I/O metric charts use [canonical error codes](/apis/design/errors#handling_errors).\nIf these error codes persist in your sources and sinks, refer to the following list for potential causes and actions you can take.\n\n- `RESOURCE_EXHAUSTED`. The project might have run out of [resource quota](/compute/quotas) for the service the source or sink is using.\n\n If the error occurs occasionally or when the **Requests per sec chart** indicates a high volume of requests being made, then this might indicate that you have reached an [API rate limiting quota](/service-infrastructure/docs/rate-limiting) and need to increase the quota.\n- `DEADLINE_EXCEEDED`. Source or sink might have timed out reading or writing a large batch of data. Check the latency chart and worker logs. If the error persists, [contact support](/support-hub).\n\n- `INVALID_ARGUMENT`. Parameters specified to the source or sink might be malformed (such as a Pub/Sub topic). Check configuration of the source or sink, and check the worker logs.\n\n- `FAILED_PRECONDITION`. Check configuration of the source or sink, and check the worker logs. This could also indicate a bug.\n\n- `OUT_OF_RANGE`. Check that the resource being used by the source or sink exists (such as a Pub/Sub topic or subscription).\n\n- `UNAUTHENTICATED`. Check that the [Dataflow service account](/dataflow/docs/concepts/security-and-permissions#cloud_dataflow_service_account) has [Identity and Access Management](/resource-manager/docs/access-control-org) permissions to the specific service and relevant [APIs are enabled](/endpoints/docs/openapi/enable-api) for the project.\n\n- `PERMISSION_DENIED`. Check that the [Dataflow service account](/dataflow/docs/concepts/security-and-permissions#cloud_dataflow_service_account) has [Identity and Access Management](/resource-manager/docs/access-control-org) permissions to the specific service and relevant [APIs are enabled](/endpoints/docs/openapi/enable-api) for the project.\n\n- `NOT_FOUND`. Check that the entities being used by the source or sink exist (such as a Pub/Sub topic or subscription).\n\n- `ABORTED`. Service might not be properly handling the source or sinks attempts to read or write data. If the error persists, [contact support](/support-hub).\n\n- `ALREADY_EXISTS`. I/O might be trying to create an entity which already exists (such as a Pub/Sub topic or subscription). If the error persists, [contact support](/support-hub).\n\n- `CANCELLED`. This can occur when a Dataflow worker is shut down or source or sink logic intentionally decides to cancel attempts to read or write data.\n\n- `DATALOSS`. Indicates unrecoverable data loss or corruption occurred. You might want to create a new dataset for your sources and rerun the Dataflow job.\n\n You might also see if there are any backup and restoring instructions available for the underlying Google Cloud service.\n- `UNKNOWN`. Service might be down. Check for updates on [Cloud Status Dashboard for more information](https://status.cloud.google.com/).\n\n- `INTERNAL`. Service might be down. Check for updates on [Cloud Status Dashboard for more information](https://status.cloud.google.com/).\n\n- `UNAVAILABLE`. Service might be down. Check for updates on [Cloud Status Dashboard for more information](https://status.cloud.google.com/).\n\n- `UNIMPLEMENTED`. The source or sink attempted to use the service in an invalid way. Your pipeline might be misconfigured. If the error persists, [contact support](/support-hub)."]]