Known Issues & How to Report a Problem

Current known issues affecting app installs and runs, and how to report problems so they get triaged fast.

Insight Cloud's sync engine automatically keeps Snowflake permissions, databases, and roles matched to what happens in the product. Installs, upgrades, and access changes. When it runs behind or fails, you may see permission errors, hanging installs, or runs that never start. This page lists what we know about and exactly how to report anything you hit.

Resolved. No action needed

  • Permission errors right after install or upgrade: runs now wait for provisioning to finish before executing. You no longer need to wait before running a newly installed app.

  • Wrong app version used on scheduled runs after publishing a new version (SBT 1.0 apps): fixed.

  • Missed scheduled runs (SBT 1.0 apps): now detected automatically, with notifications.

Open. Report every occurrence

  • Missing table grants that retrying never fixes: a run fails with "Object … does not exist or not authorized" and retries do not help. Report immediately with the app name and table name. Retrying will not resolve this one. (First, rule out the pipeline grant issue in Prerequisites for App Installs.)

  • Runs that appear to run forever (SBT 1.0 apps): the run may have finished without Insight Cloud being notified. Report it; do not repeatedly re-trigger.

  • Sync delays: installs or permission changes taking noticeably long. Report even if you are not sure it is an error.

  • _test suffix mismatch with mapping models (SBT 1.0.7): run-app writes mapping model targets with the _TEST suffix while the app looks for the unsuffixed name. --no-suffix is a workaround where safe. Report cases.

  • Marking existing models private does not hide their tables (SBT 1.0.10+): works for new apps and new models; the fix for existing installed apps is in progress. Report cases.

How to report. Contact Us, every time

Use the Contact Us link inside Insight Cloud for everything: install failures, run failures, waits, errors, and ideas.

  • Report even when you are unsure whether it is a real error or a sync delay. If you are waiting, report it.

  • Duplicates are welcome. How often something happens drives prioritization.

  • Rule of thumb: if you are doing anything you did not used to do, including waiting. Report it.

  • Include the app name, variant, what you did, the exact error text, and roughly when it happened. Mention deadlines so urgent items move up the triage queue.

Every submission is triaged, cataloged, deduplicated, and routed to the right team. Follow your reports at insightcloud.featurebase.app. Questions you want to discuss go to your product contact or the collab channel instead.

Related articles