Yes, I opened case #CS1065347 for the BESExplorer service randomly crashing.
I ended up stopping the service after it crashed again just after a couple of days I had closed the case.
The other “Limitation” is that when I run queries like the following:
(((value of results from(bes properties "CustomProperty") of it as string)| ("")) %26 "%252522" )of bes computers whose (name of it contains "Hostname")
Where I dynamically add doble quotes to the results to later build a json object using session relevance, the escaped characters are needed for the WR service to properly parse the request and I get the results I need. However, when I run the exact same query in BigFix Explorer it just can’t parse it and returns en error.
I have many queries that I have built over the years based on what the REST API running on the WR service can handle, and changing all these queries will requiring a lot of work for my org.
I didn’t open a case for this, though.