Skip to main content
If Vizdom fails to establish a connection to your database, work through these checks in order:1. Verify your credentialsConfirm the username, password, host, port, and database name are correct. Try connecting with the same credentials from a local client (such as psql or MySQL Workbench) to rule out a credentials issue.2. Check your firewall rulesVizdom connects from a fixed set of IP addresses. You may need to add these to your database server’s allowlist. To get the current list of Vizdom egress IPs, go to Settings → Integrations → Network or contact support@flowstateai.com.3. Verify SSL settingsIf your database requires SSL, make sure the Require SSL option is enabled on the data source connection form. If your database uses a self-signed certificate, upload it in the SSL certificate field.4. Check port accessibilityConfirm that the port your database listens on (for example, 5432 for PostgreSQL) is accessible from the public internet or from Vizdom’s IP range, depending on your network setup.5. Test the connectionAfter making changes, click Test connection on the data source settings page. The error message shown here often points directly to the underlying issue (for example, Connection refused vs. Authentication failed).If you’re still stuck, share the exact error message with support@flowstateai.com.
Slow dashboard load times are usually caused by one or more of the following:Add indexes to queried columnsIf your data source is a relational database, check that the columns used in filters, joins, and ORDER BY clauses have appropriate indexes. Unindexed queries on large tables are a common cause of slow loads.Enable cached modeVizdom can cache query results to avoid re-running expensive queries on every page load. To enable it, open the dataset settings and turn on Cache results. Set a cache duration that balances freshness with performance (for example, 15 minutes for non-real-time data).To enable caching on a dashboard:
1

Open dashboard settings

Click the ··· menu on the dashboard and select Settings.
2

Enable cache

Toggle Enable query cache and set the cache duration.
3

Save

Click Save. The next dashboard load will warm the cache; subsequent loads will use it.
Reduce the number of chartsEach chart on a dashboard runs at least one query. Dashboards with more than 15–20 charts can become slow regardless of query speed. Consider splitting a large dashboard into multiple focused dashboards.Filter at the dataset levelIf a dataset pulls millions of rows and filters are applied only at the visualization layer, move the filters into the dataset SQL query or dataset filter settings to reduce the data transferred.
If the AI Insights feature returns empty results or an error, check the following:Data source must be connectedAI Insights requires a live data source connection. Go to Settings → Data Sources and confirm the data source status shows as Connected (green). If it shows an error, resolve the connection issue first — see Cannot connect to database above.Dataset must be configuredAI Insights works at the dataset level, not directly on the data source. Make sure you have created at least one dataset from your data source. Navigate to Data → Datasets and confirm a dataset exists and has a valid query or table selected.Dataset must have dataRun a preview query on the dataset (open the dataset and click Preview) to confirm it returns rows. AI Insights cannot generate insights from an empty dataset.Column types must be set correctlyAI Insights uses column type metadata (number, date, text) to choose appropriate analyses. If columns are typed incorrectly, open the dataset settings and correct the column types under Schema.If AI Insights still doesn’t work after these checks, contact support@flowstateai.com with the name of the dataset and a description of what you’re seeing.
PDF export uses a headless browser to render the dashboard before generating the PDF. Very large dashboards can cause the renderer to time out before all charts finish loading, resulting in a blank or partially rendered PDF.Known issue: Dashboards with more than 20 charts, or charts that contain very large datasets, may produce blank PDF exports. This is a known limitation.Workarounds:
  • Split the dashboard into smaller dashboards with fewer charts, then export each one separately.
  • Use PNG export for individual charts (click the ··· menu on a chart and select Export as PNG), then combine the images manually.
  • Enable query cache on the dashboard (see Dashboard is loading slowly) so charts render from cached data during export, which is significantly faster.
  • Use the scheduled report feature to send a PDF by email. Scheduled reports use a longer rendering timeout (60 seconds vs. 15 seconds for on-demand exports), which handles most large dashboards.
We’re working on improvements to the PDF export renderer. If this is blocking a critical workflow, contact support@flowstateai.com to discuss alternatives.
If a team member doesn’t receive their invitation email:1. Check the spam or junk folderInvitation emails come from noreply@flowstateai.com. Ask the recipient to search their inbox and spam folder for this address.2. Resend the invite
1

Go to Settings → Team

Scroll to the Pending invites section.
2

Find the invite

Locate the pending invite for the email address.
3

Resend

Click Resend invite. A new invitation email will be sent and the previous link will be invalidated.
3. Check your custom SMTP setupIf your workspace uses a custom SMTP server (configured under Settings → Integrations → Email), the invite may be failing to deliver due to a misconfiguration. Try sending a test email from the SMTP settings page to verify delivery. If the test fails, fix the SMTP configuration or temporarily disable it to fall back to Vizdom’s default sender.4. Check for email filtering rulesSome organizations block external email domains. Ask the recipient’s IT team if there are any email filtering rules that might be blocking mail from flowstateai.com.
A 401 Unauthorized response from the Vizdom API means the request could not be authenticated. The most common causes are:Expired or revoked API keyAPI keys do not have a set expiry date by default, but they can be manually revoked. Go to Settings → API Keys and check whether the key you’re using is still listed as active. If it has been revoked or deleted, generate a new key.Incorrect Authorization header formatThe API requires a Bearer token in the Authorization header. Make sure the header is formatted exactly as:
Authorization: Bearer YOUR_API_KEY
Common mistakes include omitting Bearer, adding extra spaces, or sending the key as a query parameter instead of a header.Regenerating an API key:
1

Go to Settings → API Keys

Find the key you want to replace.
2

Revoke the old key

Click Revoke next to the key. This immediately invalidates it.
3

Generate a new key

Click New API key, give it a name, and copy the key value. Store it securely — Vizdom only shows the full key once.
4

Update your integration

Replace the old key with the new one in any applications or services using the API.
For full API authentication documentation, see the authentication reference.
Still need help? Reach out to the Vizdom support team.

Email support

Contact the Flowstate AI support team at support@flowstateai.com. Include your workspace slug, a description of the issue, and any relevant error messages to help us respond quickly.