I have a dashboard that uses joins with subsearches and when it runs for me and others it shows no errors. But for a few people when they run it, it runs/completes but has the red warning error with a message like [subsearch] search process did not exit cleanly exit code=255. When I inspect the job it says this "[subsearch]: No matching fields exist."
I'm confused why this warning isn't showing up from everyone. Is there a way to ensure this message doesn't show up?
It sounds like it could be permissions or limits.
Subsearches and joins have limits that can affect how they will work
Is it always consistent for the same user or varies?
If no matching fields exist, it may be those users don't have permission to access the data being searched.
It is consistent for the same users as far as I know. The user is a power user but I've asked another power user and they don't see the warning issues.
The results returned are similar for me and the user who is getting the warning error.