Skip to content

Troubleshoot Tag Resource Mapping

This guide provides solutions for common tag resource mapping issues in the BigQuery connector.

Tag Resource Mapping Failed

If you encounter an error message indicating that a tag resource mapping operation failed, follow these steps to resolve the issue.

Error Symptoms

You may see an error in the connector logs or portal similar to:

Text Only
1
2
3
4
Tag resource mapping failed: Tag '<tag_name>' was not created properly in BigQuery. 
The tag is missing required property 'policyTagName'. 
Please ensure the tag is created correctly with proper taxonomy and project 
configuration before mapping to columns.

This error indicates that the tag resource mapping operation failed because the tag does not have the required properties set by the connector, preventing the mapping from being applied to columns.

Resolution Steps

Follow these steps in order to resolve the issue:

Step 1: Remove Tag Resource Mappings

  • Navigate to the Privacera portal.
  • Remove all tag–resource mappings for the affected tag.
  • Ensure all columns are unmapped from the tag.

Step 2: Delete the Tag from Portal

  • Delete the tag definition from the Privacera portal.
  • This will trigger the tag deletion process in the connector.

Step 3: Verify Tag Deletion in BigQuery

  • Wait 2–3 minutes for the connector to process the deletion.
  • Verify in BigQuery that the tag no longer exists in the taxonomy.
  • Check the connector logs to confirm successful tag deletion.

Step 4: Clean Service-Side References (if needed)

  • If the tag still appears in BigQuery after deletion from the portal:
    • Manually remove all occurrences of the tag from BigQuery.
    • Ensure no policy tags or taxonomy entries remain.
    • This ensures a clean state before recreation.

Step 5: Restart the Connector

  • Restart the BigQuery connector to ensure a clean state.
  • Wait for the connector to complete its initialization cycle.

Step 6: Recreate the Tag and Mappings

  • Create the tag definition again in the Privacera portal.
  • Verify tag creation success by checking:
    • Connector logs for successful tag creation.
    • BigQuery console to confirm the tag exists in the taxonomy.
  • Only after successful verification, create the tag resource mappings

Critical Reminders

  • Do NOT create or delete tags directly in BigQuery when portal mappings or policies exist. Always manage tags through the Privacera portal.

  • Always verify that tag creation is successful via the connector before proceeding with tag resource mappings. If tag creation fails, subsequent operations will also fail.

  • Check connector logs after each operation to ensure successful completion before moving to the next step.

Prevention Best Practices

To avoid tag resource mapping failures:

  • Always verify tag creation in BigQuery before creating tag resource mappings
  • Monitor connector logs for any tag creation errors
  • Ensure proper taxonomy and project configuration before creating tags
  • Do not manually modify tags in BigQuery when using Ranger tag-based masking
  • Wait for connector sync cycles to complete before making subsequent changes