CS_Tools Archiver Identify Issue

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

cs_tools self info
Fetching latest CS Tools release version timed out after 0.33s
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Info snapshot taken on 2025-10-29 │
│ │
│ CS Tools: 1.5.12 │
│ Python Version: Python 3.9.20 (main, Aug 23 2025, 13:51:39) │
│ [GCC 8.5.0 20210514 (Red Hat 8.5.0-28)] │
│ System Info: Linux (detail: Linux-4.18.0-553.77.1.el8_10.x86_64-x86_64-with-glibc2.28) │
│ Configs Directory: /apps/opt/application/cs_tools/.config/cs_tools │
│ Activate VirtualEnv: source "/apps/opt/application/cs_tools/.config/cs_tools/.cs_tools/bin/activate" │
│ System Python Path: /apps/opt/application/cs_tools/.config/cs_tools/.cs_tools/bin/python │
│ Platform Tags: linux-x86_64

Description

Below is the command used - I wanted to tag objects that are not viewed nor modified in last 180 days

cs_tools tools archiver identify --config vztsprod_tsadmin --content all --recent-activity '180' --recent-modified '180' --tag Test_Stale_180_NoViews_NorMDFD_Del_102925 --syncer csv:///apps/opt/application/cs_tools/cs_tools_syncers/cstools_prod_csv_def.toml --ignore-tags Stale_360d_NoViews_NorMDFD_Ignore --no-prompt >> /apps/opt/application/cs_tools/cs_tools_syncers/csv_files/prod/Archive_Stale_Objects/logs/Identify_Test_102925.log 2>&1

I observed that one of the liveboard which is viewed "1 day ago" got tagged. Can we check why this is happening?

Considering adding a log file.

No response

Start by reviewing the reported cs_tools tools archiver identify command and its Identify_Test_102925.log output, then trace how --recent-activity 180 is applied. Reproduce the case with the supplied configuration and confirm that a liveboard viewed one day ago is excluded from tagging, with the log explaining the result.