This is an unhandled error! when running searchable metadata

[AlexanderStephenson]

First Stop

• I have read and agreed to the ThoughtSpot LICENSE.
• I understand that if I have a critical issue with ThoughtSpot, I should reach out to my designated Account Executive and Customer Success Manager instead of cs_tools.

Platform Configuration

Runninng against - TS Cloud 10.14.0 cl-75
Using Cs tools 1.6.5 self info below.
I have checked the config file provided and this works.

Description

I have previously run the following command with no issues. I ran this with the current version I had installed and after failing I have updated to 1.6.5 and still get the same error.

cs_tools tools searchable metadata --syncer csv://tomls/csv_syncer.toml --config prod

some example have double quotes around the syncer parameter but this does not seem to have any effect.

cs_tools tools searchable metadata --syncer "csv://tomls/csv_syncer.toml" --config prod

I have also tried changing the directory on the toml from single quotes to double quotes, based on the first log file attached.

in the log file attached there are a few error messages
"Org feature is disabled."
"Roles feature is disabled"
whoopsie, something went wrong!

I have checked the config and this passes.

Considering adding a log file.

2025-12-05T14_36_58.log

2025-12-05T14_55_04.log

[AlexanderStephenson]

I have tried adding a default Org ID = 0 to my config, but this gives a different error as the Orgs are not enabled.

[AlexanderStephenson]

We have enabled Orgs and the same issue is thrown. This appears to be something to do with the meta data for groups that is inconsistent between our migrated on prem to cloud cluster and our new cloud based non prod cluster.

The same command, but switching config from prod to nonprod works.

[AlexanderStephenson]

In our environment a Local group did not have a "modified" field while cs_tools code "api_transformer.py" is looking for that key value.
Since it is not available cs_tools throw error = "KeyError: 'modified'"

This is a bug in CS Tools where the API response is missing the modified field in the group header. This can happen with certain system groups or groups that have never been modified.

After modifying this group in our cluster and re-fetching the group through the same API the is successful.

Once it populates - cs_tools issue should be resolved.