Codespace running in recovery mode or not at all.

[ALcit144]

Select Topic Area

General

Body

For the past week, I have been trying to complete two separate programming assignments for my introductory Python class, but the codespaces for each either run in recovery mode or not at all. If the Cengage outage from last week is still persisting, that seems to be the source of the problem, and I am still unable to do anything about it on my end other than opening a support ticket as well as a discussion post. If I am lucky enough to make it past the initial startup screen after a wait that is much longer than I am comfortable with, I am eventually presented with an error message indicating that the environment is currently running in recovery mode and I cannot do anything. My instructor was generous enough to extend these assignments through this week, and I do not wish to take advantage of their flexibility with deadlines nor do I want to fall even more behind in my coursework. In the meantime, I have started a discussion post here, and as of the time of writing, I am currently in the process of submitting a support ticket related to the matter at hand.

[jonattasmoraes]

Hello 👋

Codespaces entering recovery mode usually means the environment failed to start because of an internal issue on GitHub's side. This often happens after service outages like the Cengage incident you mentioned.

You can try the following while waiting for support:

• Delete the Codespace and create a new one.

• Check the GitHub status page at https://www.githubstatus.com/

• Try launching the Codespace in a different region.

• Try another browser or an incognito window.

If none of these options work, then opening a support ticket was the right step. Recovery mode normally indicates a backend issue that only GitHub can fix.