How to Report Bugs and Issues in Retool

Before filing a bug report, spend 5 minutes ruling out common causes. Check: (1) Is this a configuration issue? Try the operation in a fresh app with minimal components. (2) Is this a browser issue? Test in Chrome and Firefox — if it works in one, note the difference. (3) Is this a permissions issue? Check the Debug Panel for 403/401 errors. (4) Does the issue reproduce for other users? If it's only you, check your browser cache and cookies. If it's everyone, it's more likely a platform bug.

Navigate to Settings → About to find your Retool version number (e.g., 'Retool 3.25.0'). For self-hosted, also note your deployment method (Docker, Helm, etc.). Open your browser's DevTools (F12). Note your browser name and version (Chrome 120, Firefox 121, etc.). Note your OS (macOS 14, Windows 11). For self-hosted issues, note your infrastructure details (AWS, GCP, Kubernetes, Docker Compose). Include all of this in your bug report — version-specific bugs are common and this information is essential for triaging.

Open browser DevTools (F12 or Cmd+Option+I). Switch to the Console tab. Reproduce the bug. Copy all error messages and stack traces that appear in red. For network errors, switch to the Network tab, reproduce the bug, find the failed request (red status code), right-click → Copy as cURL. This provides the full HTTP request/response context that Retool support needs. Screenshot the console if copy-pasting is difficult.

1// Console errors to include in bug report:
2// - Red error messages with full stack traces
3// - Network 4xx/5xx responses
4// - JavaScript exceptions
5// - Any retool-specific warnings
6
7// Example console error to capture:
8// TypeError: Cannot read property 'data' of undefined
9//   at eval (query1.js:42:18)
10//   at RetoolContext.executeQuery (retool.js:1234:5)

The fastest way to get a bug fixed is to provide a minimal reproduction: a new Retool app with only the components and queries necessary to demonstrate the bug, nothing else. Create a new app, add the minimum components, and reproduce the issue. Share the app (if on a shareable plan) or describe the exact configuration steps in your report. A minimal reproduction removes irrelevant variables and makes it easy for Retool support to understand the exact issue.

Choose the right channel: Community forum (community.retool.com) for general questions, feature requests, or issues affecting the free plan. Support portal (support.retool.com) for bugs on paid plans (Pro, Business, Enterprise). In the support portal, click 'Submit a request' and fill in: subject (brief description), description (detailed reproduction steps), Retool version, browser, OS, and attach screenshots/console log. For Enterprise customers with critical issues, mark priority as 'Urgent' for faster SLA response.

A good bug report has four sections: (1) Summary — one sentence describing the bug. (2) Steps to reproduce — numbered list of exact steps from a fresh browser. (3) Expected behavior — what should happen. (4) Actual behavior — what actually happens, including error messages. Include: 'I added a Table component, connected it to a SQL query returning 100 rows, and enabled editable columns. When I edit a cell and click Save, the page shows a blank white screen instead of saving the changes.'

1// Template for bug report description:
2
3**Summary:**
4[One sentence description]
5
6**Steps to reproduce:**
71. Create a new Retool app
82. Add a [Component] component
93. Set Data source to [{{ expression }}]
104. Perform [specific action]
115. Observe [what happened]
12
13**Expected behavior:**
14[What should happen]
15
16**Actual behavior:**
17[What actually happens, with error messages]
18
19**Retool version:** 3.25.0
20**Browser:** Chrome 120
21**OS:** macOS 14.2
22**Console errors:** [paste here]
23
24**Additional context:**
25[Any other relevant information]