# Step 7: When it doesn’t just work

> For the complete documentation index, see [llms.txt](https://developers.thoughtspot.com/docs/llms.txt)

Source: https://developers.thoughtspot.com/docs/tutorials/spottercode-embed/step-07

# Step 7: When it doesn’t just work

Worth building into the guide on purpose, because it happens on every real project.

## Scenario: outdated SDK version

Your project was scaffolded months ago and still points at an older Visual Embed SDK version. You ask for a feature that only exists in a newer release, and the generated code doesn’t run.

Fix: name the version explicitly and ask what changed.

```
Update my Liveboard embed code to the latest Visual Embed SDK version
and list any breaking changes from my current version in the documentation.
```

## Scenario: vague follow-up gets a vague answer

"Make the dashboard better" will not produce useful code. Keep prompts scoped to one outcome:

-   Not: "Can you customize the embed?"
    
-   Instead: "Fetch the documentation for `LiveboardEmbed` and summarize the available customization options." Then pick one and ask for it by name.
    

## General troubleshooting checklist

-   No response or not loading → confirm SpotterCode is enabled for this project and the MCP server is reachable.
    
-   Slow responses → break the ask into smaller, sequential prompts instead of one large request.
    
-   Response looks wrong → check which tool the agent actually called. Refine the prompt for specificity before assuming the tool is broken.
    
-   Don’t ask it to infer SpotStay’s business logic. Anything not in the docs or the SDK, you still have to specify yourself.
    

[← Previous]({{navprefix}}/tutorials/spottercode-embed/step-06) [Next →]({{navprefix}}/tutorials/spottercode-embed/summary)