GitHub Actions "Run workflow" button gets stuck in loading state

[yasendudin-sg]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Code Search and Navigation

Body

Description: After GitHub introduced the new side panel for manually running workflows, the "Run workflow" button can get stuck in a loading state when navigating back to the workflow page using the browser's Back button.

Reproduction Steps:

1. Open a GitHub Actions workflow.
2. Click "Run workflow" to open the side panel.
3. Trigger a workflow run.
4. Use the browser's Back button to return to the previous page.
5. Open the "Run workflow" side panel again and attempt to trigger another run.

Expected behavior: The "Run workflow" button should reset to its default state, allowing users to trigger another workflow run.
Actual behavior: The button remains stuck in a loading state with a spinning indicator, preventing users from triggering another run.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[dhyyan]

Thank you for reporting this issue. This behavior is indeed a client-side routing/state preservation bug introduced alongside the new Turbo/SPA (Single Page Application) navigation logic for the manual workflow side panel.
When you use the browser’s Back button, the page is restored from the browser's cache or Turbo cache, which unfortunately preserves the active loading or disabled attribute state on the DOM elements instead of re-initializing the button component.

🔄 Temporary Workarounds

Until this UI lifecycle issue is patched, you can use these methods to bypass the stuck state:

1. Hard Refresh: Performing a quick full reload (F5 or Ctrl+R / Cmd+R) resets the DOM context and restores the button to its default state.
2. Use the GitHub CLI: You can manually trigger your workflow directly from your terminal using the GitHub CLI:bash
   gh workflow run --ref
   Use code with caution.

🛠️ Next Steps for the Engineering Team

The engineering team will need to review the frontend component lifecycle for the manual trigger panel. Specifically, it needs a listener for Turbo cache restoration events (like turbo:before-cache or turbo:load depending on the framework) to explicitly tear down the loading state or reset the component's state machine.

[yasendudin-sg]

Yeah hard refresh and CLI usage are possible work-arounds just wanted to inform you about it, thanks!