Error log
Server failures and errors reported by browsers. Administrators use it to find the cause of a problem and to brief support.
This page applies to the System and project configuration stage.
How to do it
- Filter. Choose the period, the source (server or browser) and the status.
- Read the row. Each row shows the time, the kind, the path, the code and the message.
- Copy the trace ID. Give the trace ID to support. It links the entry to the server logs.
Good to know
- The kinds are API call, network, render and unhandled.
- Status 0 means the browser got no response.
- The log is not the audit log. It records faults, not changes to project data.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: