Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG][code-analyzer] Flow engine isn't producing results file

Open
  • Is something wrong?
#1,958 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python, typescript
Domain
devtools, tooling

Research direction

Start with FlowScannerCommandWrapper.js at runFlowScannerRules and the FlowScannerEngine.runRules entry point named in the stack trace. Reproduce the issue with the supplied sf code-analyzer command on Windows and trace why flowScannerResultsFile.json is absent. Done means the Flow engine produces the expected report without the ENOENT error.

Written by the indexing model from the issue text.

Description

Have you tried to resolve this issue yourself first?
  • I confirm I have gone through the above steps and still have an issue to report.
Bug Description

flow:UnexpectedEngineError null:undefined:undefined no such file or directory,open 'C:\Users\DANIEL~1.GAL\AppData\Local\Temp\code-analyzer-Tea130\run-2025_12_19_13_39_40_449\flow\flowScannerResultsFile.json'

Output / Logs
1   1 (Critical)   flow:UnexpectedEngineError   null:undefined:undefined   The engine with name 'flow' threw an unexpected error: Error: ENOENT: no such file or directory, open 'C:\Users\DANIEL~1.GAL\AppData\Local\Temp\code-analyzer-Tea130\run-2025_12_19_13_39_40_449\flow\flowScannerResultsFile.json'
                                                                             at async open (node:internal/fs/promises:642:25)
                                                                             at async Object.readFile (node:internal/fs/promises:1279:14)
                                                                             at async RunTimeFlowScannerCommandWrapper.runFlowScannerRules (C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-flow-engine\dist\python\FlowScannerCommandWrapper.js:52:36)
                                                                             at async FlowScannerEngine.runRules (C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-flow-engine\dist\engine.js:104:34)
                                                                             at async CodeAnalyzer.runEngineAndValidateResults (C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-core\dist\code-analyzer.js:389:35)
                                                                             at async C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-core\dist\code-analyzer.js:276:29
                                                                             at async Promise.all (index 0)
                                                                             at async CodeAnalyzer.run (C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-core\dist\code-analyzer.js:283:38)
                                                                             at async RunAction.execute (file:///C:/Users/daniel.gallo/AppData/Local/sf/node_modules/@salesforce/plugin-code-analyzer/lib/lib/actions/RunAction.js:39:25)
                                                                             at async RunCommand.run (file:///C:/Users/daniel.gallo/AppData/Local/sf/node_modules/@salesforce/plugin-code-analyzer/lib/commands/code-analyzer/run.js:86:9)



=== Summary

Found 1 violation(s) across 0 file(s):
    1 Critical severity violation(s) found
Steps To Reproduce

sf code-analyzer run --rule-selector flow --target C:\xxxxx\unpackaged\main\default\flows\Test_Security_Flow.flow-meta.xml --output-file C:\xxxx\Test_Security_Flow.flow-meta.xml.pmd.html --view table

Expected Behavior

THE CORRECT REPORT WITHOUT DE ISSUE FROM PLUGIN ENGIE FLOW

Operating System

windows 11

Salesforce CLI Version

@salesforce/cli/2.116.6 win32-x64 node-v24.11.1

Code Analyzer Plugin (code-analyzer) Version

flow 1.0.5

Node Version

24.11.1 (Currently using 64-bit executable)

Java Version

openjdk 25.0.1 2025-10-21 LTS OpenJDK Runtime Environment Temurin-25.0.1+8 (build 25.0.1+8-LTS) OpenJDK 64-Bit Server VM Temurin-25.0.1+8 (build 25.0.1+8-LTS, mixed mode, sharing)

Python Version

Python 3.14.2

Additional Context (Screenshots, Files, etc)
59.0 Check_Permission Check Permission 200 100 Default Outcome Admin_Only and true Allowed Admin Only Check_Permission Admin_Only Test Security Flow BuilderType Flow Flow
Workaround

No response

Urgency

Hight

Dominant language
TypeScript
Stars
240
Forks
52
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forcedotcom/code-analyzer

All issues in forcedotcom/code-analyzer

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.