# Status badges for named workflows

**URL:** <https://discuss.circleci.com/t/status-badges-for-named-workflows/48550>\
**Category:** Running Tests\
**Created:** [July 5, 2023, 4:34pm UTC](https://discuss.circleci.com/t/status-badges-for-named-workflows/48550 "2023-07-05T16:34:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bravehager](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/bravehager/32/33336_2.png) [@bravehager](https://discuss.circleci.com/u/bravehager)\
**Post date:** [July 5, 2023, 4:34pm UTC](https://discuss.circleci.com/t/status-badges-for-named-workflows/48550/1 "2023-07-05T16:34:24Z")

</div>

Is there any plan to support status badges for individual (named) workflows? Relying on a branch makes it difficult to run multiple independent workflows for a given project.

Right now we have a primary build/test workflow that’s integrated into our release process. Engineers rely on a status badge to have visual feedback that CI is green. We have a secondary, scheduled CI job that is _expected_ to fail occasionally.

When a release coincides with the scheduled CI job, it causes our status badge to go red, which is frustrating. Moreover, engineers can accidentally re-run the scheduled workflow (unaware it isn’t the primary build/test workflow), leading to even more confusion.

---

<div class="post-metadata">

**Author:** ![harshp](https://avatars.discourse-cdn.com/v4/letter/h/58956e/32.png) [@harshp](https://discuss.circleci.com/u/harshp)\
**Post date:** [July 13, 2023, 6:26pm UTC](https://discuss.circleci.com/t/status-badges-for-named-workflows/48550/2 "2023-07-13T18:26:44Z")

</div>

I’d love to see this as well. My use case is a little different, where we have test frameworks with workflows setup for different target applications. I’d love to have a way to get each application’s status badge.