Skip to main content

Troubleshooting: Widget Issues

Widget shows a blank iframe​

Probable causes:

  • Your JavaScript has an error that stops execution before any content renders.
  • The widget is still loading data.

What to do:

  1. Open the Console tab in the widget editor. Look for red error messages.
  2. Check that your HTML has the elements your JavaScript references (matching id attributes).
  3. If the widget worked before and now shows blank, check whether the data connection was removed or its config was changed.

getData() returns undefined or errors​

Probable causes:

  • The connection name in your code doesn't match the name in the Data panel.
  • The data connection isn't attached to the widget.
  • The data source config isn't accessible to you.

What to do:

  1. Open the Data tab in the widget editor. Confirm the connection is listed.
  2. Check that the name you pass to getData("name") matches exactly (case-sensitive).
  3. If the connection uses a config you don't have access to, ask your admin to grant access.

getData() returns an empty array​

Probable causes:

  • The underlying table or query returned no records.
  • Filters on the data connection are too restrictive.

What to do:

  1. Go to the data connection's detail page and review its filters.
  2. Try removing all filters temporarily to confirm the source has data.
  3. For SQL connections, test the query directly in your database tool to verify it returns results.

Console shows "Failed to fetch" or network errors​

Probable causes:

  • The data source config has incorrect credentials or the server is unreachable.
  • A SQL or MQTT server is behind a firewall that blocks the Crow's Nest worker.

What to do:

  1. Ask your admin to test the data source config in Organization Settings.
  2. For SQL connections, verify the database server allows connections from Cloudflare Workers IP ranges.
  3. For MQTT, confirm the broker URL uses WebSocket protocol (ws:// or wss://).

Widget works in editor but not on a dashboard​

Probable causes:

  • The widget relies on a connection that the dashboard viewer doesn't have access to.
  • Dashboard input values aren't being passed correctly.

What to do:

  1. Check that the dashboard viewer's role gives them access to the required data source configs.
  2. If the widget uses getValue(), confirm that the dashboard has input defaults set for those keys.
  3. Open the widget in the editor directly to confirm it still works independently.

Chart doesn't render​

Probable causes:

  • Chart.js code is in the wrong tab (should be in the Chart.js sub-tab, not the JavaScript tab).
  • A variable referenced in the Chart.js section isn't defined in the JavaScript section.

What to do:

  1. Move chart creation code to the Chart.js sub-tab. This section runs after the JavaScript section and shares its scope.
  2. Make sure any data variables you reference in Chart.js are defined with let or var (not const inside a block) in the JavaScript section so they're accessible.
  3. Check the Console tab for Chart.js-specific errors.

Widget loads slowly​

Probable causes:

  • The data connection fetches a large number of records.
  • Caching is disabled on a Tulip connection.

What to do:

  1. If using a Tulip connection, enable caching to avoid fetching all records on every load.
  2. Add filters to your data connection to reduce the record count.
  3. For SQL connections, optimize your query (add WHERE clauses, LIMIT, or indexes).

Need more help?​

If none of the above resolves your issue, use the Feedback page (accessible from the navigation bar) to submit a bug report with details about what you see.