Hi,
In PAD, go to:
Actions > Error Handling > Begin Error Handling
Add your entire flow logic (or key steps) inside the Try block.
Use the On block error path to define a Catch block.
In the Catch block:
Log the error to a file using Write text to file
Include:
CurrentDateTime()
%Exception.Message%
%Exception.ErrorCode%
Optionally hardcode the Correlation ID if it’s part of a specific known issue
Step 2: Write error log to a local file
Use the action:
vbnet
Write text to file
→ Path: C:\Logs\pad_error_log.txt
→ Text to write:
%CurrentDateTime()% - Error occurred: %Exception.Message% - Code: %Exception.ErrorCode%
→ Append to file: ON
This ensures that all runtime errors are silently caught and logged for post-analysis.
Step 3: (Optional) Send an email if flow fails
You can add:
Send email action via Outlook or SMTP in the Catch block
Attach the error message and timestamp
Step 4: Turn Off System Pop-ups (Avoid Stopping Flow)
PAD shows pop-up errors only if exceptions are unhandled. Once inside a Try-Catch block, these are suppressed.
If you're seeing pop-ups despite using error handling:
Ensure the error is not thrown from outside the Try block (like a misconfigured machine trigger, unattended login, etc.)
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.
Regards,
Riyaz
Share
Report
All responses (
Answers (
2,818
