# Troubleshooting

## Databricks Authentication Fails

| Possible Cause | Resolution |
|  --- | --- |
| Invalid PAT | Verify the PAT is still valid and has not expired. Regenerate if needed. |
| Service principal not in workspace | Ensure the service principal has been added to the workspace. |
| Incorrect hostname | Confirm the Databricks workspace hostname format (e.g., `dbc-e1c6a646-1e07.cloud.databricks.com`). |
| Incorrect HTTP path | Verify the SQL warehouse or cluster HTTP path in Databricks workspace settings. |
| IP access list blocking | Ensure Treasure Data server IPs are added to the Databricks allow list. |


## PAT Creation Fails for Service Principal

| Possible Cause | Resolution |
|  --- | --- |
| "User does not have permission to use tokens" | The initial PAT must be created by a workspace admin using `databricks token-management create-obo-token`. Service principals cannot create their own first token. |
| OAuth M2M profile used instead of admin profile | Use an admin profile (`--profile <admin-profile>`) when running the OBO command, not the service principal's OAuth profile. |


## Parent Segment Upload Fails

| Possible Cause | Resolution |
|  --- | --- |
| Invalid JSON | Validate your JSON with a linter (e.g., `jq . parent_segment_config.json`). |
| Wrong `connectionId` | Confirm the ID matches your saved Databricks authentication in Integration Hub. The `connectionId` can be found in the URL of the authentication detail page. |
| Missing `catalog` field | Databricks requires the `catalog` field in master, attributes, and behaviors definitions. Ensure it is present in all entries. |
| Table/schema/catalog not found | Verify all catalog, schema, and table names exist in Databricks and match exactly (case-sensitive). |
| Missing columns | Ensure `keyColumn`, `tableKey`, `masterKey`, and all `column` values exist in the referenced tables. |


## Segment Counts Show Zero

| Possible Cause | Resolution |
|  --- | --- |
| Empty Customers table | Verify the Customers table has data: `SELECT COUNT(*) FROM <catalog>.<schema>.customers;` |
| Key mismatch | Confirm that unified profile identifier values in Behaviors tables match those in the Customers table. |
| Permission issues | Ensure the service principal has `SELECT` on all referenced tables in Unity Catalog. |


## Cannot Access CAS UI

| Possible Cause | Resolution |
|  --- | --- |
| Feature not enabled | Contact Customer Success to verify your account has Composable Audience Studio enabled. |
| Browser cache | Clear browser cache and reload the page. |
| Account permissions | Contact Customer Success to verify your account has CAS permissions. |