[Feedback] InternalExecutionErrors in sfca v5.12

[varsh-acn]

Feedback

Hi,

We are using SFCA v5.12 and we are still seeing InternalExecutionError coming in the logs for our SFGE scan. This is our SFGE settings:
sfge:
java_thread_count: 10
java_thread_timeout: 300000

The command we use is: sf code-analyzer run --rule-selector sfge --target <sfge_target_file> --config-file --output-file <output_file>

I can see from this ticket (#1497) there have been improvements made from v5.11 onwards but we do still see errors such as 'Path evaluation timed out after 300000 ms' , does this mean the scanner is unable to scan through the enter .cls file? Because if we don't set a timeout the scan doesn't seem to end. Please help to advise, thanks

Context

No response

Suggestions

No response

Additional Information

No response

Are you interested in contributing to this project?

Yes, I'd like to contribute.

[nikhil-mittal-165]

Hi @varsh-acn,

Thanks for the detailed report! A few things that would help us investigate further:

1. Could you share the full stack trace of the InternalExecutionError you're seeing? That'll help us pinpoint exactly where the failure is occurring.
2. Regarding the timeout — the 'Path evaluation timed out after 300000 ms' message means the SFGE engine hit your configured 5-minute limit while evaluating paths through a particular method or class. This doesn't necessarily mean the entire .cls file is skipped — SFGE will time out on individual path evaluations and move on, but complex files with deeply nested logic can trigger this frequently. Could you let us know roughly how many target files your project includes? That'll help us assess the scope.
   3.On the output file — after the run completes, is your output file partially populated (results for some files, but not all), or is it empty/missing entirely? This distinction will tell us whether the errors are causing a full abort or just skipping specific evaluations.

As a quick sanity check, you might also try running without the java_thread_timeout override to see if the default (30s per path) produces more complete results — ref: Code Analyzer v5.11.0 release notes.

FYI do try with a shorter timeout period, you will see a significant improvement in the execution of sfge