[GH-ISSUE #85] The log ends with injection-vuln completing but there's no final phase completion or report generation. #27

Closed
opened 2026-02-27 07:20:03 +03:00 by kerem · 5 comments
Owner

Originally created by @robertclarkson on GitHub (Feb 7, 2026).
Original GitHub issue: https://github.com/KeygraphHQ/shannon/issues/85

The log ends with injection-vuln completing but there's no final phase completion or report generation. The workflow appears to have stopped after the vulnerability-exploitation phase without producing a final consolidated report.

No clue about why it stopped

Originally created by @robertclarkson on GitHub (Feb 7, 2026). Original GitHub issue: https://github.com/KeygraphHQ/shannon/issues/85 The log ends with injection-vuln completing but there's no final phase completion or report generation. The workflow appears to have stopped after the vulnerability-exploitation phase without producing a final consolidated report. No clue about why it stopped
kerem closed this issue 2026-02-27 07:20:03 +03:00
Author
Owner

@ezl-keygraph commented on GitHub (Feb 8, 2026):

Hi @robertclarkson, thanks for reporting

  1. Can you please share the output logs of the failed event from temporal which will be helpful to reproduce this issue
    Open http://localhost:8233/namespaces/default/workflows
    Open the failed workflow run, click on the failed event in the Event History

  2. Did you use any other model/provider other than the default?

<!-- gh-comment-id:3867363308 --> @ezl-keygraph commented on GitHub (Feb 8, 2026): Hi @robertclarkson, thanks for reporting 1. Can you please share the output logs of the failed event from temporal which will be helpful to reproduce this issue Open http://localhost:8233/namespaces/default/workflows Open the failed workflow run, click on the failed event in the Event History 2. Did you use any other model/provider other than the default?
Author
Owner

@robertclarkson commented on GitHub (Feb 8, 2026):

  1. the web UI is always down 503 when i go to check it after a failed attempt.
  2. No, I used claude
<!-- gh-comment-id:3868013726 --> @robertclarkson commented on GitHub (Feb 8, 2026): 1. the web UI is always down 503 when i go to check it after a failed attempt. 2. No, I used claude
Author
Owner

@robertclarkson commented on GitHub (Feb 8, 2026):

Oops i closed this by accident, and cant reopen

<!-- gh-comment-id:3868014054 --> @robertclarkson commented on GitHub (Feb 8, 2026): Oops i closed this by accident, and cant reopen
Author
Owner

@ezl-keygraph commented on GitHub (Feb 9, 2026):

Reopened @robertclarkson, please try running the scan again and check if the temporal is up in docker

<!-- gh-comment-id:3869968284 --> @ezl-keygraph commented on GitHub (Feb 9, 2026): Reopened @robertclarkson, please try running the scan again and check if the temporal is up in docker
Author
Owner

@keygraphVarun commented on GitHub (Feb 24, 2026):

We've made significant updates/refactors since then. Please open a new issue if it still persists.

<!-- gh-comment-id:3948624614 --> @keygraphVarun commented on GitHub (Feb 24, 2026): We've made significant updates/refactors since then. Please open a new issue if it still persists.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/shannon-KeygraphHQ#27
No description provided.