Arcade Intersect function negative buffer stopped working (June 2026 update)

[JohnO_Donnell]

One of our most heavily trafficked web applications stopped working after June update. Popups for the parcels layer, which found intersecting features across a host of other feature layers, just went into infinite loop for most selected features. Culprit seems to be the negative value I had for the Buffer operation. Changing all Arcade expressions to use a centroid intersection instead seems to have fixed the immediate issue, but I'd eventually like to move back to negative buffers, as they provide a more accurate intersecting value.

[David_McRitchie]

Hey John,

I may have had some simliar behaviour on a case I recently had. If you create a new feature do we find the values for calculated fields successfully populating or not?

If we create the feature and then do a separate edit to move the feature geometry do we find Arcade expressions working?

Might be worth raising a support case with your distributor, especially if this is a release specific issue,