Troubleshooting Known Issues
You can read about issues, limitations, and troubleshooting steps for Tamr Cloud.
Account Settings
| Issue | Resolution |
|---|---|
| Login fails with SSO enabled. | If login fails and SSO is enabled, contact your organization’s IT department to verify you have been assigned the correct permissions to log into Tamr Cloud. |
Data Products
| Issue | Resolution |
|---|---|
| Data product refresh fails when refresh of one of its source datasets fails or is cancelled. |
To avoid running a data product with out-of-date data, data product refresh fails if refreshing one of
its source datasets fails or is stopped via the Jobs API. To refresh the data product, first successfully refresh the source.
This does not apply to legacy data products, which will run using previous source data if source refresh fails. |
Sources
| Issue | Resolution |
|---|---|
You are unable to upload files when the content-type metadata field isn’t set to text/csv.
|
Tamr Cloud supports only csv files for upload. |
| 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. |
| Data values must be only Basic Latin characters to display properly. | Current limitation. |
| File upload fails. | Confirm that your file meets all requirements for upload. For example, ensure that your header rows do not include trailing commas, which result in blank headers and cause the file upload to fail. Make any necessary adjustments, and then retry. If you continue to receive an error, contact Tamr ([email protected]) for assistance. |
| GCS source configuration is invalid. |
Replace any spaces in the file path with %20. For example, you would replace source /file source.csv with source%20/file%20source.csv.
|
| Schema mapping step is marked as incomplete. | If you add new columns to a source, you need to redo schema mapping for that source. |
Publishing
| Issue | Resolution |
|---|---|
| When publishing to Snowflake, publishing fails the schema has changed 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. |
Jobs
| Issue | Resolution |
|---|---|
| You can run up to 5 concurrent jobs. Additional job requests return the following error: 429 Too Many Requests. | Current limitation. |
Legacy Data Products
| Issue | Resolution |
|---|---|
| The status of individual steps is not accurate while the flow runs. | Known issue |
| 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.
|
| 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:
|
Updated 6 days ago