"Sorry, something went wrong. Reload?" after creating my first action

I tried making my first GitHub action here:


The action looks at who modified certain files in a pull requet, then adds them as reviewers.  Note that, yes, this is *like* the CODEOWNERS, but we want package maintainers to be able to add their names to a maintainer list in their own package.py files instead of always updating a single file.

I added my action to main.workflow and attempted to trigger it with a pull request here:


Now, my Actions tab doesn’t work and just says “Sorry, something went wrong. Reload?”.  I’m not sure how best to get debug output from the actions, or how to understand what’s wrong.  Any pointers?


Noticed the same thing as well today in a brand new action.

+1 brand new action and stuck on reload (for what it worth :  the initial commit had been overwritten)

1 Like

Same problem here. At first I thought it was due to bad formatting of my workflow, but when I revert to a known working revision, the problem persists.

Did you find any solution for this?

Incredibly frustrating … Can’t do any testing when this happens… No known solution and there’s been no word from any Github employees.

our repo migreted to the new system uning yml and now it works just fine :) 

I was having this issue too and I saw that there was an error in the console. I opened that link and it took me to the “Sign in using SSO” link, after I signed in, it started working.

Weird thing is, this is my own repo and doesn’t belong to the organization that the SSO belongs to. Seems like a bad auth implementation to me.

1 Like

I’m seeing this as well.

I’d like to demo GitHub actions at a Meetup but it would be tough if I can get passed this error message

This may be a clue in my case. I can’t verify console errors on my phone but conincidentally an org I belong to enables some form of Okta which I can only find info on here https://help.github.com/en/articles/about-authentication-with-saml-single-sign-on.

What’s strange is the places I am prompted for this auth. This forum was one. The repos I am am using GitHub actions with are not part of that organization but see this issue regardless.

I had the same issue. Based on the browser logs I figured out that it had to do with it wanting to sign in using SSO for an organization that has nothing to do with the repository in question but fails to open the dialog:

For example, this if from FireFox:

An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing. actions
Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
Content Security Policy: The page’s settings blocked the loading of a resource at https://github.com/PerMalmberg/Smooth/actions (“frame-ancestors”).

And this from Chrome:

Refused to display 'https://github.com/login/oauth/authorize?response_type=code&redirect_uri=https%3A%2F%2Flaunch-editor.github.com%2Fauth%2Fcallback&state=<code>&client_id=<another code>' in a frame because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'none'".

I got the request to sign in using SSO for the same organisation when signing in to this forum too. (what if I’m part of several orgs with forced SSO?!)

Now that I am signed in with SSO, I can access my Github Actions page again.

Clearly forced SSO from an organization has too wide reach, in addition to the failure to open the dialog.

confirmed, its an sso integration that causing this issue for me as well. I can’t disable this because this sso is for my work place’s github organization. 

Thanks for reporting this - we’re investigating this issue.


Any updates from the investigation? I am still facing this issue.