The I/O metric charts usecanonical error codes.If these error codes persist in your sources and sinks, refer to the following list for potential causes and actions you can take.

• RESOURCE_EXHAUSTED. The project might have run out ofresource quota for the service the source or sink is using.

  If the error occurs occasionally or when theRequests per sec chart indicates a high volume of requests being made, then this might indicate that you have reached anAPI rate limiting quota and need to increase the quota.

• 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.

• 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.

• FAILED_PRECONDITION. Check configuration of the source or sink, and check the worker logs. This could also indicate a bug.

• OUT_OF_RANGE. Check that the resource being used by the source or sink exists (such as a Pub/Sub topic or subscription).

• UNAUTHENTICATED. Check that theDataflow service account hasIdentity and Access Management (IAM) permissions to the specific service and relevantAPIs are enabled for the project.

• PERMISSION_DENIED. Check that theDataflow service account hasIAM permissions to the specific service and relevantAPIs are enabled for the project.

• NOT_FOUND. Check that the entities being used by the source or sink exist (such as a Pub/Sub topic or subscription).

• ABORTED. Service might not be properly handling the source or sinks attempts to read or write data. If the error persists,contact support.

• 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.

• 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.

• DATALOSS. Indicates unrecoverable data loss or corruption occurred. You might want to create a new dataset for your sources and rerun the Dataflow job.

  You might also see if there are any backup and restoring instructions available for the underlying Google Cloud service.

• UNKNOWN. Service might be down. Check for updates onCloud Status Dashboard for more information.

• INTERNAL. Service might be down. Check for updates onCloud Status Dashboard for more information.

• UNAVAILABLE. Service might be down. Check for updates onCloud Status Dashboard for more information.

• 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.