Hi @postwick
In order to find the line/activity that is throwing the error, You can use “Call Stack”.
The activity throwing the error will be displayed with the activity name “Exception thrown by…”.
When you Double-click on it, it will take you to the spot where the exception is thrown.
Regardless, it is better to have log messages to track which step you’ve reached.
If this solves your query, Do mark it as a solution.
Happy Automation 