Peter Zhang
Feb 19, 2026 23:29
GitHub’s workflow dispatch API now returns run IDs, eliminating the necessity for customized polling options when triggering automated workflows programmatically.
GitHub has quietly solved one of many extra annoying ache factors for builders automating their CI/CD pipelines. The workflow dispatch API endpoint now returns run IDs straight in its response—a small change that eliminates hours of workaround code.
Beforehand, triggering a workflow by way of API gave you nothing however a 204 No Content material standing. You knew the workflow began, however good luck determining which run was yours with out polling the API repeatedly or constructing customized monitoring techniques. That is now mounted.
The replace, introduced February 19, 2026, introduces a brand new optionally available parameter referred to as return_run_details. Set it to true, and you will get a 200 OK response containing the workflow ID, API URL, and workflow URL. Skip the parameter, and the outdated 204 conduct continues—backward compatibility preserved.
GitHub CLI customers working model 2.87.0 or later get this robotically. Fireplace off gh workflow run and you will see the created run’s URL plus the gh run view command to test on it. The CLI now defaults return_run_details to true.
This issues for anybody constructing automation on prime of GitHub Actions. Suppose deployment orchestration techniques, batch processing pipelines, or any tooling that should observe what it spawned. The earlier method—polling the runs endpoint and attempting to match timestamps or commit SHAs—was fragile and rate-limit hungry.
The timing is notable. GitHub previewed its Agentic Workflows idea simply two days earlier on February 17, signaling deeper funding in programmatic workflow management. And the platform continues to be recovering reputationally from a serious outage affecting hosted runners on February 2 that disrupted CI/CD pipelines throughout the ecosystem.
For context, GitHub bumped the utmost workflow_dispatch inputs from 10 to 25 again in December 2025, one other quality-of-life enchancment for complicated automation eventualities.
The function is stay now within the REST API. Documentation is offered in GitHub’s Actions workflow occasions information for anybody able to ditch their customized monitoring hacks.
Picture supply: Shutterstock
