This page lists known issues with Cloud DLP, along with ways you can avoid or recover from these issues.
Issues common to inspection and profiling operations
These entries are applicable to both BigQuery inspection and profiling operations.
Rows with row-level security can't be scanned
Row-level security policies can prevent Cloud DLP from inspecting and profiling the protected BigQuery tables. If you have row-level security policies applied to your BigQuery tables, we recommend that you set a TRUE filter and include the service agent in the grantee list:
- If you're profiling data at the organization or folder level, include the service agent of the container project in the grantee list.
- If you're profiling data at the project level or running an inspection job on a table, include the service agent of the project in the grantee list.
BigQuery inspection issues
These entries are only applicable to inspection operations on BigQuery data. They don't affect data profiles.
Exported findings do not have values for the row_number field
When you configure Cloud DLP to save findings to BigQuery, the
field in the generated BigQuery table is inferred at the time the input
table is scanned. Its value is nondeterministic, can't be queried, and can be
null for inspection jobs.
If you need to identify specific rows where findings are present, specify
inspectJob.storageConfig.bigQueryOptions.identifyingFields at job creation
Identifying fields can be found in the generated BigQuery table, in
BigQuery profiling issues
These entries are only applicable to profiling operations on BigQuery data. For more information, see Data profiles for BigQuery data.
Organizations or projects with more than 500 million tables
Cloud DLP returns an error if you attempt to profile an organization or project that has more than 500 million tables. If you encounter this error, you can send your feedback through email to firstname.lastname@example.org.
If your organization's table count has more than 500 million tables, and you have a project with a lower table count, try to do a project-level scan instead.
For information about table and column limits, see Data profiling limits.
The inspection template must be in the same
region as the data to be profiled. If you have data in multiple regions, use
multiple inspection templates—one for each region where you have data.
You can also use an inspection template that is stored in the
If you include a template in the
global region, Cloud DLP uses it
for any data that doesn't have a region-specific template. For more information,
see Data residency considerations.
A stored infoType (also known as a stored custom dictionary detector) that is referenced in your inspection template must be stored in either of the following:
- The same region as the inspection template.
Otherwise, the profiling operation fails with the error,
Resource not found.
VPC Service Controls
Using this feature with VPC Service Controls zones is not officially supported. If you try scanning data inside a VPC Service Controls zone, let us know what issues you run into by sending an email to email@example.com.
Intelligent document parsing
This section contains known issues related to document parsing.
DocumentLocation object isn't populated
location.content_locations.document_location.file_offset field isn't
populated for Intelligent Document Parsing scanning mode.