I've seen this one or twice before but has anyone else ever seen an N/search return

undefined

for search results rather than

search.Result

? If so, is it a NS bug or were you able to find a root cause? I didn't see anywhere in the docs that would suggest that

undefined

should be expected.

if you

save()

your search, what does it give you in the UI?

One example of this was a search in the UI - and apparently it shows results when run in the UI. Only provides

undefined

to script - and notably this script and the search have not changed - it used to run as expected and get

search.Results

back

Is the script running with the same permission set?

Not sure - presume so. Will have to check. Still, I would expect NS to return an error or no results - not

undefined

where

search.Record

should appear (per the docs and previous experience)