Hi, I'm using variables APIs and Metadata parameterization for connection and tables. It used to be works fine. but In our quite new org, I'm observing SECURE_STORE_ERROR error with v26.04.

Error Code: SECURE_STORE_ERROR Incident Id: 84e41b82-71e0-433b-9108-4d9b8fe16e75
Error Message: com.thoughtspot.common.ThoughtSpotException:  Not Found

This error has been occurring on "Manage tables" button on connection, model and table column preview. What kind of check should be performed?

message has been deleted

What you described (fails specifically on Manage tables, model, and table column preview) is consistent with a secure credential/secret lookup problem rather than general metadata API syntax. From official docs, the most relevant required checks are: 1. Variables exist in the org For metadata parameterization, variables must be available in that instance/org (use variable search API to verify). 2. Permissions are present You need edit access to the target Connections and Tables you’re parameterizing. 3. Connection metadata is valid for table discovery “Manage tables” and column preview rely on connection metadata retrieval; if the referenced auth/secret entry is missing, table/column introspection can fail with not-found style errors. Given your error text: -

SECURE_STORE_ERROR

-

ThoughtSpotException: Not Found

- Happens on flows that read connection internals (Manage tables/preview) the first high-probability check is: the parameterized secret/credential reference used by this new org cannot be resolved in its secure store (missing variable value, missing mapping, or invalid reference after org migration/cloning). ### Suggested check order (fastest path) - Verify variables in this org via variable search API. - Confirm each required variable has a valid value in this org/environment. - Open the connection definition and validate parameterized fields resolve to existing variables. - Re-test table introspection using Data connection APIs (with/without column data) to isolate whether failure is at secure-store lookup or downstream DB metadata access. - Confirm user/role has edit on connection + table. - If still failing, raise support with your Incident Id (

84e41b82-71e0-433b-9108-4d9b8fe16e75

) and exact build (

v26.04

) since this looks like a backend secure-store resolution path.

@Kentaro Yoshida | Commune Inc is the solution from SpotterCode working?

@Swarnika These check lists has already checked from my side. so I need to get assistance. 🙏

@Kentaro Yoshida | Commune Inc - Please raise a support ticket for this. Its a bug

@utsav.kapoor Hi utsav, Sure. I have created support ticket. This is script based operation and it can be reproduced on your side, too. Case No. 00433237

I faced the similar issue and realized sensitive variables are not replaced properly. I was able to reproduce this consistently with connection variable for private key part of connection. When I updated the value with wrongly formatted private key, thoughtspot was throwing same issue even after update the correct values with operation = REPLACE. I also have a ticket but nothing have been done yet.

It seems that the bug has been identified and the fix is ​​underway.