Understanding ProcFu Error Logs

ProcFu maintains comprehensive error logs to assist you in debugging issues within your apps. To access the error logs, navigate to "Run Logs" in the sidebar or visit the following link: ProcFu Error Logs. Note that this section covers all aspects of ProcFu except for Data Syncs, which have their own separate logs.

Understanding the Table

• Date: The date when the error was logged.
• Type: The source of the error, which can be one of the following: App, Function, PS Script, UI Action, Raw Code, Widget, PHP Code, Cron Task.
• ID: The identifier of your app, cron job, or script associated with the error.
• PID/Sess: The server process ID (PID), used to group logs by processes for server-related issues.
• Lvl: The severity level of the error, which can be either Warning or Error.
• Message: The actual error message describing the issue.

Filtering Errors

If you are looking for a specific error, you can use filters to narrow down the results. Useful filters include Date, Type, and ID. For example, you can start by filtering errors by date to view all errors from a specific day. Then, hold down the Shift key and click on the ID of an app or script to filter all errors from that day for that particular ID. You can progressively refine your search by using Shift + mouse click until you have a manageable set of logs to review.

Email Logs

To closely monitor error logs, you can enable email notifications by clicking the "Email Logs ON/OFF" option above the table on the right side. Enter the email address where you would like to receive error notifications and click the "Update" button to save your settings.

Here’s an example of the email message you will receive:

ProcFu has encountered an error.
Element Type: App
Element ID: DABbASDuF6fN
PID/SessID: 2490206
Error Message: Error Demo From App

In this email:

• Element Type: Represents the type of error source.
• Element ID: Indicates the specific App ID associated with the error. In this case, it is "DABbASDuF6fN".
• PID/SessID: This field may not be meaningful for general debugging, so it can typically be ignored.
• Error Message: Provides a description of the error encountered, such as "Error Demo From App".

Follow

Keep the "Follow" button checked to enable auto-refresh of the page whenever new errors are logged. This ensures you are always viewing the most current error information without having to manually refresh the page.

Notes

• If the error message includes something like Object not found on line 6, note that the line numbers refer to lines of code, excluding any default comments. Default comments are not counted as code lines.