After the June 2026 ArcGIS Online update, every indicator element using advanced formatting (Arcade) in my org now renders topText, middleText, and bottomText overlapping on a single baseline instead of stacked top / middle / bottom. This happened across multiple dashboards at once with no changes on my end — they rendered correctly the day before the update and broke the day of.
A few things I've confirmed:
The dictionary is still being parsed fine — topTextColor, middleTextColor, bottomTextColor, and backgroundColor all still apply correctly. Only the vertical layout of the three text areas is broken; they collapse to the same anchor point. Font and text size also look different from before.
This is contrary to the current Indicator documentation, which states the visualization is divided into three areas (top, middle, bottom) that scale to fit. Those three areas no longer render as separate regions.
The Dashboard Indicator Formatting Arcade profile is unchanged (still v1.11), and every key I'm using is still documented as valid. The expression contract didn't change — only the rendering did.
I tried adding explicit topTextMaxSize/middleTextMaxSize/bottomTextMaxSize values and removing/normalizing backgroundColor. Neither fixes it, which points to the indicator's text layout rendering rather than the expression.
It reproduces from a clean two-line return:
return { topText: 'TOP LINE', topTextColor: '#003B5C', middleText: 'MIDDLE LINE', middleTextColor: '#f07820', bottomText: 'BOTTOM LINE', bottomTextColor: '#388E3C'}
Expected: three stacked lines. Actual: all three overlapping on one baseline.
Workaround that's holding for now: move the top and bottom lines out of the expression into the General tab Top caption / Bottom caption fields via {expression/attributeName}. That restores correct stacking but loses dynamic per-state text color (captions take a static color) and means hand-editing every indicator.
Is anyone else seeing this after the June update? And can anyone from the Dashboards team confirm whether it's a known regression? This is on operational dashboards so a fix or official workaround would be much appreciated.
EDITED TO ADD: The June 2026 release notes describe an 'Improved indicator text scaling' change ('standardized text scaling,' 'new text settings give authors precise control over sizing and emphasis'). This standardized text-scaling change appears to be the source of the regression. The advanced-formatting documentation and the Arcade release notes do not expose any new return-dictionary property to control the new scaling, so authors using advanced formatting have no documented way to opt into correct rendering, the three text areas simply collapse onto one baseline. The release also states it 'continues to fully support existing Dashboards,' which this regression contradicts.
Hi @NateClements with this update the TextMaxSize arcade property was removed. Do you continue to see the same behavior if you use TextMaxHeight and TextWeight arcade properties?
@StephanieW , thanks for the quick reply. That seems to have fixed our issue. However, I don't see this documented anywhere in the update notes. If it was, can you point me to the resource so I can keep an eye on it for future updates? I'll keep testing this morning but this is extremely helpful. Thank you.
this update looks like a joke, my indicators have lost any logic....
Another interim workaround to consider is adding something like middleTextMaxHeight:30 to the return expression.
I think this explains why the update broke these indicators. I had set up this dashboard as an embedded stats bar and it was working before the update yesterday. I had some custom code in there with spacers so the text would stay a uniform size, luckily all I need to do is add a brace on the end of the code to fix it as you can see in the left-hand indicator. I guess the code got truncated when TextMaxSize was removed? Some of these dashboards are public facing, so this is very disappointing. I'm hoping a patch will be released promptly to fix this an the other issues we have noticed with this rollout