Skip to main content
All CollectionsPortal-X Pages
Global | Logs | Unreadable Request Logs
Global | Logs | Unreadable Request Logs

Monitoring incomplete and inexecutable client APIs requests

Jason Liang avatar
Written by Jason Liang
Updated over a week ago

The most common cause for these errors is networking errors (we didn't receive the full request), bad serialization of JSON objects, or security issues (bad packet ID, secret, etc.). Through this page, you can

  • View the list of all the unreadable requests with details of the requests and other helpful pieces of information.

  • View the details of each unreadable request and origin info

Click an individual log row, it will open the log Details blade.

  • From the above details dialog window, you will find the origin IP and other helpful pieces of information about this client API request. You can click the Copy icon on this window to copy the content of this request and paste it into your other editors/tools for debugging.

  • Note: ProfileId will show up in the Profile column only for these requests that have user sessions associated with them.

Did this answer your question?