Known issues

Known issues

This page lists the known issues that you might run into while embedding ThoughtSpot in your app, or when using the embedded interface or making REST API calls.

Version 9.12.5.cl🔗

Issue DescriptionSymptoms, conditions, and workaround

The full view of the Liveboard is not visible when users switch between tabs

Symptom:
When users switch between tabs on an embedded Liveboard, the height of the Liveboard page changes and cuts the Liveboard content.

Conditions
This issue was observed on ThoughtSpot embedded instances using Visual Embed SDK versions below v1.29.0, with the fullHeight property set to true.

Workaround
To resolve this issue, upgrade to Visual Embed SDK v1.29.0 or later.

Version 9.12.0.cl🔗

Issue DescriptionSymptoms, conditions, and workaround

Exporting and reimporting TML in YAML format returns an error.

Symptom:
On exporting and reimporting TML in YAML format in the REST API v2 Playground, the following error message is returned: Invalid YAML/JSON syntax in file. Conditions:
This issue occurs because when reimporting TML invalid characters are added to the TML YAML content in the Playground resulting in an invalid syntax error. Workaround: We recommend the following steps to work around this issue:

  1. On the REST API v2 Playground, export the TML in YAML format.

  2. Copy the edoc output from the API response in the code panel.

  3. Paste it in a text editor such as Sublime.
    For example, "guid: a162289a-c1ab-427e-9985-8fb5f7c7e539\nliveboard:\n name: Liveboard 1\n"

  4. Check if the output is enclosed in quotation marks ("). Remove the quotation marks and update the TML text as shown here:
    guid: a162289a-c1ab-427e-9985-8fb5f7c7e539\nliveboard:\n name: Liveboard 1\n

  5. On the Import Metadata TML API page, go to body > metadata_tmls parameter.

  6. Add / remove objects in that list based on how many TML objects you want to import.

  7. Click VIEW JSON to view the object properties in JSON format.
    The request body JSON appears as shown in this example:

    {
  "metadata_tmls": [
    "metadata_tmls3"
  ],
  "import_policy": "PARTIAL",
  "create_new": false,
  "all_orgs_context": false
}

  8. Replace metadata_tmls3 with the text copied from step 4. Ensure that the text you copy doesn’t include additional characters and quotation marks.

    {
  "metadata_tmls": [
    "guid: a162289a-c1ab-427e-9985-8fb5f7c7e539\nliveboard:\n  name: Liveboard 1\n"
  ],
  "import_policy": "PARTIAL",
  "create_new": false,
  "all_orgs_context": false
}

  9. Execute the API call by clicking Try it Out.

    If you still get an error, try out the steps shown in this video:

Version 9.10.0.cl🔗

Issue DescriptionSymptoms, conditions, and workaround

Deployment via version control API fails after the destination Org is renamed.

Symptom: Deploying TML from the /api/rest/2.0/vcs/git/commits/deploy API endpoint fails when the destination Org is renamed and results in new files being created in the GitHub repository.
Condition: This issue occurs because ThoughtSpot creates mapping files to match GUIDs of source and destination environments. These mapping files use the name of the organization to look up the GUIDs that need to be set on the TML deployed in the destination Org.
Workaround: To work around this issue:

  1. Log in to the GitHub account integrated with your ThoughtSpot instance.

  2. Navigate to the GitHub repository that stores ThoughtSpot files.

  3. Select the branch that stores configuration files.

    CI/CD Git branch

  4. Navigate to the folder ending with […​].mapping.

    CICD Git branch

  5. Check the .json file with the old name of your Org. If it exists, delete it: these are the new mappings created after the latest deployment.

    Note

    You may have to delete the matching files in ThoughtSpot that have been created as part of this deployment operation.

  6. Locate the .json file with the old name of your Org and rename the file with the new name of the Org. <my_old_org_name>.json → <my_new_org_name>.json

After you complete these steps, the /api/rest/2.0/vcs/git/commits/deploy endpoint will use this mapping file and deploy to the destination Org successfully.

The download menu actions are not visible in the embedded view

Symptom: Although the Action.Download enumeration is defined in the visibleActions array, the Download menu options are hidden in the embedded view.
Condition: This issue occurs on ThoughtSpot instances with 9.10.0.cl or earlier versions.
Workaround: If you are using the visibleActions array to show or hide actions on a visualization or Answer, include the following download action enumerations along with Action.Download in the array:

* Action.DownloadAsCsv
* Action.DownloadAsPdf
* Action.DownloadAsXlsx
* Action.DownloadAsPng

Version 9.5.0.cl and 9.6.0.cl🔗

Issue DescriptionSymptoms, conditions, and workaround

The View Liveboard link in Liveboard schedule notifications do not show the custom URL

Currently, ThoughtSpot doesn’t support customizing the View Liveboard URL for Liveboard schedule notifications.

When you try to update the list of CORS hosts on the Security Settings page, you may notice a domain validation error if a subdomain with a wildcard, for example .*.domain.com, is already added to the CORS allowed list on your ThoughtSpot instance.

To resolve this issue, add an escape character (\) after the wildcard in the domain URL string as shown here:

.*\.domain.com

Version 9.2.0.cl🔗

Issue IDDescriptionSymptoms, conditions, and workaround

SCAL-147773

The Export Liveboard Report API endpoint returns the incorrect payload error.

Symptom: A REST API request to download a Liveboard in the PNG format returns an error.

Condition: This issue occurs when a user tries to download a given Liveboard as a PNG file via a REST API call to the /api/rest/2.0/report/liveboard endpoint.

Workaround: None

Version 9.0.0.cl🔗

Issue IDDescriptionSymptoms, conditions, and workaround

SCAL-142933

The REST API v2.0 session login endpoint does not return session cookies.

Symptom: The /api/rest/2.0/auth/session/login endpoint does not return session cookies after a successful API call.

Condition: This issue is observed when a REST client tries to log in to ThoughtSpot with basic authentication using the REST API v2.0 session/login endpoint.

Workaround: Use one of the following options:

  • Use the /api/rest/2.0/auth/token/full API endpoint to get a bearer token and use it in the Authorization header to authorize your subsequent API requests.

  • Use the REST API v1 endpoint /tspublic/v1/session/login to log in to ThoughtSpot and obtain session cookies.

Version 8.10.0.cl🔗

Issue IDDescriptionSymptoms, conditions, and workaround

SCAL-117106

The User account gets locked after a single bad token login attempt

Symptom: If a user attempts to log in to the embedded ThoughtSpot app with an invalid token, the application locks that user’s account.

Condition: This issue is observed in ThoughtSpot deployments with the trusted authentication setup.

Workaround: If you are using the trusted authentication method to authenticate your users, make sure the getAuthToken function in the SDK returns a fresh token for each re-login. Avoid using older tokens to renew a user session.

Version 8.9.0.cl🔗

Issue IDDescriptionSymptoms, conditions, and workaround

SCAL-117106

The User account gets locked after a single bad token login attempt

Symptom: If a user attempts to log in to the embedded ThoughtSpot app with an invalid token, the application locks that user’s account.

Condition: This issue is observed in ThoughtSpot deployments with the trusted authentication setup.

Workaround: If you are using the trusted authentication method to authenticate your users, make sure the getAuthToken function in the SDK returns a fresh token for each re-login. Avoid using older tokens to renew a user session.

SCAL-126662

The visualizations with no data take a long time to load in an embedded Liveboard.

Symptom: In the Liveboard classic experience mode, when chart visualizations have no data, they clog the render queue and slow down the Liveboard rendering process. The PDF download function also does not work on such Liveboards.

Condition: This issue is observed in ThoughtSpot deployments with 8.4.0.cl or 8.4.1.sw or later release versions.

Workaround: None

Version 8.8.0.cl🔗

Issue IDDescriptionSymptoms, conditions, and workaround

SCAL-128033

The REST API v2 Playground Beta does not load request parameters for some API endpoints.

Symptom: Some REST v2 API Beta endpoints may not show request parameters in the Playground.

Condition: This issue is observed in ThoughtSpot deployments with 8.7.0.cl and 8.6.0.cl release versions.

Workaround: Use REST API v1 endpoints for production use cases.

SCAL-117106

The user account gets locked after a single bad token login attempt

Symptom: If a user attempts to log in to the embedded ThoughtSpot app with an invalid token, the application locks that user’s account.

Condition: This issue is observed in ThoughtSpot deployments with the trusted authentication setup.

Workaround: If you are using the trusted authentication method to authenticate your users, make sure the getAuthToken function in the SDK returns a fresh token for each re-login. Avoid using older tokens to renew a user session.

Additional resources🔗