Skip to content
Smoke Multi Caller

[FAQ] Add: controlling the agent's working branch at runtime #721

Sign in to view logs

[FAQ] Add: controlling the agent's working branch at runtime

[FAQ] Add: controlling the agent's working branch at runtime #721

Triggered via pull request April 30, 2026 20:14
@chrizbochrizbo
labeled #29377
faq/issue-513-91fffa76478c9cf7
Status Startup failure
Total duration –
Artifacts –

smoke-multi-caller.yml

on: pull_request
task-a  /  pre_activation
task-a / pre_activation
task-b  /  pre_activation
task-b / pre_activation
task-a  /  activation
task-a / activation
task-b  /  activation
task-b / activation
task-a  /  agent
task-a / agent
task-b  /  agent
task-b / agent
task-a  /  detection
task-a / detection
task-b  /  detection
task-b / detection
task-a  /  safe_outputs
task-a / safe_outputs
task-b  /  safe_outputs
task-b / safe_outputs
task-a  /  conclusion
task-a / conclusion
task-b  /  conclusion
task-b / conclusion
task-c  /  pre_activation
task-c / pre_activation
task-c  /  activation
task-c / activation
task-c  /  agent
task-c / agent
task-c  /  detection
task-c / detection
task-c  /  safe_outputs
task-c / safe_outputs
task-c  /  conclusion
task-c / conclusion
Fit to window
Zoom out
Zoom in

Annotations

1 error
Invalid workflow file: .github/workflows/smoke-multi-caller.yml#L17
The workflow is not valid. .github/workflows/smoke-multi-caller.yml (Line: 17, Col: 3): Error calling workflow 'github/gh-aw/.github/workflows/smoke-workflow-call-with-inputs.lock.yml@f4a84ca3a4789ff588217b3da6e38ab4d45f0abc'. The nested job 'activation' is requesting 'actions: read', but is only allowed 'actions: none'.