View collapsing intermittently for a subset of users

Summary

On a Retool Cloud app (case management), a subset of end users—all on Chrome—intermittently had their app view/screen 'collapse' with no ability to expand or review context, occurring sporadically from Aug 20–27, 2026 (notably Aug 27, 1:30–2:15pm ET); it can't be reproduced on the reporter's machine and doesn't reproduce by resizing the window in DevTools.

AI Response

Intermittent, user-specific 'collapsing' of an app view on Chrome most closely matches known layout-width regressions where an app's Max width or a panel unexpectedly resets/shrinks under certain screen or session conditions rather than a true expand/collapse control. As a first step, explicitly pin the app/container Max width to 100% (or a fixed value) instead of leaving it on a resetting default, and have affected users hard-refresh and clear cache to rule out a stale client build. Since the issue only surfaced in a narrow window and can't be reproduced, capturing the app version, exact screen resolution/zoom level, and a screen recording from an affected Chrome user during a recurrence will be key to isolating whether it's tied to the width-reset behavior. No corroborating platform incident was found for the reported window, so the two reports below—both describing spontaneous, environment-dependent layout collapse—are the most relevant leads.

Sources

:bookmark: Spacing Max Width Resetting
A solved, actively-discussed report of an app's Max width spontaneously resetting from 100% to a fixed width, causing the view to render collapsed/narrow without any user change—closely matching the collapse symptom and offering the pin-width workaround.
:bookmark: Sidebar shrinking randomly on bigger screens
Corroborates the pattern of a Retool layout element randomly shrinking/collapsing for only certain screens/sessions while working fine elsewhere, consistent with this intermittent, subset-of-users behavior.

The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a :heart:, :+1:, or :-1:. Or by marking this post as the "Solution"! Let us know if you have any feedback here. :rocket: