Skip to content

Conversation

dataprofessor
Copy link
Contributor

Created a self-serve post for a commonly encountered "Oh no" error.

📚 Context

The "Oh no" error is a commonly encountered error in the community. This consolidated self-serve post helps to guide users on resolving this issue on their own.

🧠 Description of Changes

This post borrows existing contents while also adding additional information to provide a thorough treatment of the topic.

Created a self-serve post for a commonly encountered "Oh no" error.
@sfc-gh-dmatthews sfc-gh-dmatthews self-assigned this Jan 25, 2024
@sfc-gh-dmatthews
Copy link
Contributor

Thanks for this! If I don't get to this by the end of the week, I'll do it next week.

I need to double-check the current state of the error screens as they were updated to show a different error page when resource limits are reached. I just want to make sure which conditions lead to which error screen since the plan is to have a complete list of all error messages with diagnostic steps and explanations.

image

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants