finding-agent-runs

Locating specific GitHub Actions runs for troubleshooting involves matching timestamps, event types, and workflows associated with fullsend agents. It extracts run data via GitHub CLI commands to identify exact executions when results are missing or workflows fail.

Searching GitHub Actions logs for errors involves locating the specific workflow run and extracting its detailed output. You can search logs to pinpoint failure points and retrieve session artifacts to assist in debugging and record-keeping.

Yes, tracking different workflow events like triage, code, and review runs is supported across various dispatch scenarios. The process handles multiple event types, allowing you to locate specific GitHub Actions runs associated with issues or PRs.

The best way to retrieve session artifacts from a failed GitHub Actions run is to identify the exact execution using timestamp and event matching, then extract the artifacts for diagnosis. This supports debugging and process auditing by accessing detailed logs and session records.

Missing agent results from GitHub Actions workflow runs often indicate a workflow failure or dispatch issue. You can diagnose this by locating the exact run associated with the issue or PR and accessing its detailed logs to identify the specific error.