Why content blocks (Composable Dashboard Tiles) require a defined height at load time and cannot resize dynamically, plus where to configure and preview their sizing.
No, content blocks do not support runtime resizing today. Content blocks, also referred to as Composable Dashboard Tiles, must know their height at load time, which is why height is set in configuration rather than derived from the content inside them.
If content blocks resized dynamically as their contents changed, the surrounding dashboard would constantly shift as tiles expanded and contracted. That would create a jarring experience where the page appears to move, jiggle, or "dance" every time a tile updated.
Requiring a defined height keeps the dashboard stable, predictable, and visually consistent. Users see the same layout on every load, and neighboring tiles stay put when any one tile refreshes.
When you are building a content block, use the #/content-block-dev hashroute in sandbox environments. It provides a playground where you can configure content block settings, including sizing and other supported options, so you can preview how a tile will render before shipping it. For deeper background on how content blocks fit into the platform, see the Dynamic Content documentation in the SDK Docs.