Skip to content

Fix async runner response accounting#454

Merged
chubes4 merged 1 commit into
mainfrom
fix/453-async-runner-http-status
Jul 21, 2026
Merged

Fix async runner response accounting#454
chubes4 merged 1 commit into
mainfrom
fix/453-async-runner-http-status

Conversation

@chubes4

@chubes4 chubes4 commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Count only successful HTTP responses as accepted Action Scheduler loopback dispatches. Protected origins can return 403 or 5xx without executing the queue runner; those responses must return zero so callers can use another server-side worker path.

How to test

  1. Run php tests/workflow-async-runner-dispatch-result-smoke.php.
  2. Verify transport failures report 0.
  3. Verify mixed transport failures plus 200/204 report 2.
  4. Verify 403/503 report 0.

Closes #453.

AI assistance

  • AI assistance: Yes
  • Tool: OpenCode
  • Used for: Diagnosed a protected-runtime dispatch mismatch and added focused response-accounting coverage. Chris reviews and owns the change.

@chubes4
chubes4 merged commit 0d60d58 into main Jul 21, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Async runner counts rejected HTTP responses as accepted

1 participant