Doc HomeSupport

Troubleshooting Known Issues

You can read about issues, limitations, and troubleshooting steps for Tamr Cloud.

Suggest Edits

Curator Tables

Issue Resolution
You aren't able to configure column display in tables in the Manage Cluster Details page. When configuring column display in tables in the Manage Cluster Details page, the curator_drag_icon and Checkbox selection columns must remain selected.
Table search, sort, and filtering ignores any overrides values, and performs the action only on original data values. No current workaround. The table data displays records with override values, but when you search, sort, or filter, the action only occurs on original data values.
Table search, sort, and filtering ignores any overrides values, and performs the action only on original data values. No current workaround. The table data displays records with override values, but when you search, sort, or filter, the action only occurs on original data values.

Mastering Flow

Issue Resolution
The mastering flow fails on the Configure Attributes step. This might be caused by duplicate attribute names. Ensure that all attribute names are unique.
An error occurs when attempting to remove one or more attributes in the Configure Attributes step. Tamr Cloud now prevents you from removing this field. However, if you are using an earlier template version that does not include this restriction, you see this error when attempting to remove the required attribute that stores the display name for the entity. For each template, this attribute is:
  • B2B Site Mastering: company_name
  • Company Mastering with D&B: company_name
  • Company Mastering with Firmographic Enrichment: company_name
  • Contact Mastering: full_name
  • Healthcare Provider Mastering: full_name
  • Legal Entity Mastering: company_name
  • Patient Mastering: full_name
  • People Mastering: full_name
  • Supplier Mastering with D&B: company_name

Jobs

Issue Resolution
Filtering in the Jobs page table is case-sensitive. Current limitation.
Sorting the Jobs page table in ascending or descending order produces incorrect sorting results. No current workaround.
Scheduled source dataset refresh jobs are not listed on the Jobs page. Current limitation.

Publish Data

Issue Resolution
Publish button remains enabled while an export job is running. No current workaround.
Publishing the Entities by Similarity and Source Records by Entity datasets to Azure Synapse Analytics may fail for large files. No current workaround.
Error loading publish destinations. An error can occur when a connection used by an existing destination has been deleted or is no longer shared. If you experience this issue, contact Tamr Support ([email protected]) to correct the underlying problem.

For issues related to exporting to Snowflake, see Snowflake Known Issues and Limitations.

Scheduler

Issue Resolution
Scheduled source dataset refresh jobs are not listed on the Jobs page. Current limitation.
Scheduler does not adjust scheduled run times for daylight savings time. Once a job is scheduled, the scheduled run time is not updated for local timezone changes. Current limitation.

Snowflake

Issue Resolution
Publishing failing when fields have been removed since the last publish. You must either update the destination Snowflake table to match the updated schema or delete the destination table.

Note: If you delete the destination table before publishing, Publish recreates the table with the updated schema.
Publishing the Source Records by Entity Dataset to Snowflake fails, starting with the October 28, 2022 release. Two internally-used fields have been added to the Source Records by Entity dataset and the Apply Clustering step output: appliedRules and ruleClusterId. If you have previously published the Source Records by Entity dataset to Snowflake, you will receive an error when you attempt to re-publish the dataset due to the addition of these fields.


Before publishing, you must either update the destination Snowflake table to add these fields or delete the destination table.

Sources

Issue Resolution
You are unable to upload files from S3 when the content-type metadata field isn’t set to text/csv. To fix this issue, run the following command to update the metadata of the object, allowing you to upload the file to Tamr Cloud.


aws s3api copy-file --bucket <bucket_name> \ --content-type "text/csv" \ --copy-source <bucket_name>/path/to/file.csv \ --key path/to/file.csv \ --metadata-directive "REPLACE"

The number of source datasets is shown as “--”. Run your flow to repopulate source metrics.
For fields that contain double quoted values, the display value may include left or right quotes. No current workaround.
File rows cannot start or end with quote characters. Current limitation.
File upload preview assumes that data is comma delimited until a different delimiter is selected. No current workaround.
Data values must be only Basic Latin characters to display properly. Current limitation.
If you attempt to upload a file over the maximum file size, you receive an error with an empty error message. Current limitation.
File upload fails. Confirm that your file meets all requirements for upload. Make any necessary adjustments, and then retry. If you continue to receive an error, contact Tamr ([email protected]) for assistance.

See Requirements for Source Data for more.

Updated 17 days ago