I’ve never run into this before. Analyzer doesn’t report any errors, and there are no activities with an error icon on them. But when I try to run/debug I get:
Double-clicking it doesn’t do anything like the Error List tab does. It just opens the log message.
So how do I find where this error is occurring?
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 
You can check activities which require a datatable input/output since error message states string cannnot be conveted to datatable
Also, I don’t know wether this would work in a library but what we did when we faced something similar in a re framework was break down the flow in multiple temp xaml and check which xaml failed to compile
Just an idea - I guess I experienced such error when invalid default value was assigned to a variable or argument.
But I can’t simulate it now…
Cheers
The process is not starting. It’s failing during compilation
Yeah I didn’t really want to have to dig through it activity by activity but I guess that’s what I’m left with.
For anyone having a similar issue, it was a Filter Data Table activity where the “filtered datatable” variable was set as String in the variables pane. I don’t know why the activity doesn’t show an error icon on it like it should and it doesn’t show up in Analyzer either.
How could that be a Solution to your query “Is there any way to find the location of a compilation error” ??? 
Paul is explaining that your proposed solution, inspecting the call stack, is something that can only be done AFTER compilation, and it for identifying runtime errors, not compilation errors.
A compilation error means you cannot run the process.
@postwick Unfortunately I too have had this issue and its indeed very nasty to solve.
The only effective way I have found to do it is commit all my code, then start deleting large parts of it until the compilation error goes away.
The answer is “there isn’t any way” and the best I could do here is provide details on which activity wasn’t providing the error icon so people might know where to look in the future.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
