Retool: JavaScript API .trigger() calls were temporarily not returning query results
Timeline of updates
- resolved
From approximately 4:30 pm PT to 12:15 am PT, Retool’s JavaScript API .trigger() calls were not correctly returning query results, and were instead returning undefined (when waiting on results with async/await or .then()). We identified and fixed the bug that introduced this regression, and now all .trigger() calls work as before.
From Retool’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.retool.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Retool, started 2021-08-10 23:30 UTC, resolved after 0 min, 1 update(s).
- Title
- JavaScript API .trigger() calls were temporarily not returning query results
- Vendor
- Retool
- Date
- URL
- https://rewindex.com/company/retool/incidents/3wyw4jn65ld3
Retool profileRecent Retool incidentsAll outages on August 10, 2021Retool in August 2021MarkdownJSON