Troubleshooting

Root, billing, or workspace context errors

Symptoms

CLI reports invalid root, missing workspace, or path mismatch.

Fix sequence

looky login https://my.looky.studio <local_root>
looky whoami

cd <local_root>
looky billing list
looky billing use <billing_account_id>

cd <local_root>/<billing_account_id>/<workspace_slug>
looky status

Run billing commands from <local_root> and workspace commands from workspace root.

Validation fails before push

Symptoms

looky validate reports model, visualization, or dashboard issues.

Fix order

1. Fix source alias/runtime config issues first.
2. Fix model query definitions and names.
3. Fix visualization query and mapping references.
4. Fix dashboard item references and filters.
5. Re-run looky validate until no blocking errors remain.

Push succeeded but dashboard is wrong or missing

Symptoms

Dashboard not visible, empty, or inconsistent with expected output in my.looky.studio.

Fix sequence

looky status
looky diff
looky push
looky list visualizations
looky list dashboards

Then reload UI. If dashboard still fails, confirm visualization ids referenced in dashboard YAML exactly match published visualization ids.

Source/runtime mismatch

Symptoms

Models cannot resolve tables or data source behavior differs unexpectedly.

Fix sequence

looky sources diff
looky sources list
looky validate

Ensure aliases used in models exactly match aliases defined in runtime/sources.runtime.yml.

When to use rollback

If a push introduced regressions and quick forward-fix is not possible, use looky rollback from the same workspace root to return to the previous known-good server content state.