Skip to main content

Troubleshooting

Account access​

Sign in at studio.gnok.io/login with your organization's sign-in name (for example acme_corp), your email, and your password, plus your second factor if your account has one. Check that you verified your email; verification links are valid for 24 hours, and Resend verification email sends a new one. Use Forgot password? to reset your password, or ask your organization's administrator. If Studio says your account doesn't have access to Gnok Studio, an administrator of your organization must grant it. See account access.

Connection issues​

Check the connection selected in Studio. Connecting a client from outside Studio isn't self-service yet; email support@gnok.io to set it up. For a client that's already set up, confirm the host, port, protocol, TLS trust, and authentication method Gnok support gave you. The Studio URL is not interchangeable with the Flight SQL, PostgreSQL, query API, or catalog endpoints.

Try SELECT 1 AS connected;. If that fails, record the error and timestamp. Do not disable certificate verification or change server settings. If it succeeds but a table query fails, check the target catalog/schema and grants.

Query failures and unexpected results​

  • Check every statement's result when running a script. Earlier failures can invalidate later assumptions.
  • Confirm column types, joins, filters, null handling, object names, and the active model version.
  • Check the table snapshot and retention state for historical reads; see time travel.
  • For a stale shared tutorial, preserve your edits, close its draft tab, and reopen the current template.
  • For an internal error with a reference, include that reference in your support request. It lets Gnok investigate service logs without requiring customer server access.

Slow queries and resource limits​

Inspect query history and the query plan. EXPLAIN ANALYZE executes the query while measuring it; use it intentionally. Reduce unnecessary scans and join expansion, and use the warehouse and limits authorized for your workload. A LIMIT on output does not necessarily reduce all upstream work.

If a limit or capacity change is needed, ask your administrator or email support@gnok.io. Customers do not change worker memory settings or restart clusters.

Interrupted writes​

A timeout or lost connection does not establish whether a write committed. Inspect query history and the target state before retrying. Prefer operations with explicit identifiers or documented idempotency when building retry logic. Do not rerun a tutorial's reset statements over data you need to preserve.

AI and background workloads​

AI features are off for an organization until an organization administrator, in Studio under Operations → AI Governance, saves a monthly token budget as Available and enables a rollout policy (provider, model, operations, egress and retention approvals). Then check provider availability, the remaining budget, model input/output shape, and background identity grants. See tutorial troubleshooting.

Getting help​

Email support@gnok.io. Include your organization's sign-in name, the timestamp and time zone, query or error reference, sanitized SQL, and expected versus actual behavior. Keep passwords, access tokens, private keys, and unnecessary customer data out of the report.

Last updated on