Skip to main content

Hello community,

We have been provided some Custom Actions and Workflow Rules by a consultant and they just don’t work as promised. I’m trying to debug them myself but can’t find the tools that would inform me on the progress of the running actions/rules or where things are going wrong.

I thought the Process Monitor might be helpful when a long-running process takes place (like a Custom Action looping through and processing 100+ records) but I see nothing there.

And the Support article for Process Monitor doesn’t actually explain what Triggers the monitoring to begin! Can I cause monitoring to begin and to report out? What actions get “monitored”?

If not there, where else can I see any helpful information about why my Custom Action processed only 1 record out of the 20 I expected to load data into Financials and update each row’s status in this Custom Object?

This consultant has said that sometimes processes get ‘stuck’ without sharing how to un-stick them (or know if they’re stuck or just busy still). 

I often use updating a text field such as description at various stages of a workflow to test.  Especially where there are branches to ensure they have fired.   In the message add any variables  that are relevant to the workflow so you can see thier status at particular times 


Thanks @JimM - primitive but effective! 

… I loved the 90s and  printf() debugging 😆


sometimes you just to go ‘Old School’


Reply