The issue was due to the fact that a new record was added to an existing query and this record was not added to query tree access group assigned to user running this query.
Once the record was added to the appropriate query tree access group, issue is resolved.
This issue was noted in PT 8.50.22. In reality, the following message should be given.
The record (XXX) used by query is not available to the access group assigned to user. Hopefully they may fix this in future release.
This issue can also happen when you modify the query using a userid that has access to query record, but the user running it does not have access to it.
Query to determine all the records available to a userid.