Ok - so found a fix for our site. Because this is such a widely used package I'm not sure if this is something with newer versions of Umbraco, or just something oddly configured about our site, so I'm reluctant to submit a PR. @Anders Bjerner if this makes sense let me know and I'll be happy to submit it for review. Here’s a summary of the changes made to the code and the reasoning behind them: Changes: Check if

r.data.items

is an array: In several places where the code assumes

r.data.items

is an array, we added a check using

Array.isArray(r.data.items)

to confirm this before iterating over it. Fallback to

$values

property if items is not an array: If

r.data.items

is not an array but has a

$values

property, the code now checks if

r.data.items.$values

is an array and uses that instead. Set an empty array as a default: If neither

r.data.items

nor

r.data.items.$values

is an array, the code safely sets the relevant variable (e.g., vm.redirects) to an empty array to prevent runtime errors. Why These Changes Were Made: Avoiding runtime errors: The original code assumes that

r.data.items

is always an array, but if it isn't (e.g., null, undefined, or an object with

$values

), trying to iterate over it would throw an error. These changes ensure the code only attempts iteration when items is actually a valid array. Handling different data structures: Some API responses may return data structures with a

$values

property (e.g., serialized collections), so the code now gracefully handles such cases. Fail-safe implementation: By setting default empty arrays when no valid array is found, the code avoids unexpected crashes and keeps the system functioning even in edge cases. This logic was added in a few different files, but this is what got us up and running. Happy to share code if anyone needs it. Since it has awareness of trying to use the original or alternate way of checking items it should hopefully backward compatible as well.