Notebook (UI) unresponsive

Course (UI) is unresponsive. I cannot move move through the notebook content not check the completion checkbox. No scrolling. I believe it was after the update website version.

Hi, could you please post some gif or video of the issue, because form our side the pltaform seems to be working as expected.

Hey @duckfrost2 , plase download the video from the following link. I couldn’t upload them here because of the size limit.

Hope it could help.

@martinsferreiramiguel
Please try again now.

I apologize for that glitch. It seems that was a temporary problem while the course was being updated.

Hey @bayodesegun,
I’ve just checked. Logged out and back in again and the issue is still there. Refreshed, closed and opened website tab with no luck. It seems like nothing has changed since it is behaving exactly as before. Is there else I should do from my side?

The “report and error” from does not work neither. When I click submit it gets stuck loading indefinitely.

I think I found the problem. It should load for you now. That unit you were trying to access (Course Project) is no longer available, but the system was still trying to load it for you based on your history.

Please let us know.

@bayodesegun it is still the same. The progress bar is still at 83% and cannot get out of the same notebook page.
You could delete all progress/files previously created by me in this unit if it makes solving the issue easier. I was planning on doing the entire course again anyway.

I also noticed the simulation window never finishes loading. It keeps on showing the “Loading simulation…” after more than 20 min.

@martinsferreiramiguel Please try again. I removed those history files earlier, but I later found two more history files lurking somewhere :cold_sweat:

The simulation issue might be related to this. Let’s fix this first and then see if the simulation problem is still there.

@bayodesegun still the same. This time, I deleted all history/cookies and tried a different browser and it is still the same.

It’s fixed now.

I’m sorry about the back-and-forth; more things were involved than I thought.
@martinsferreiramiguel

Great! It seems to be working now. Thanks for the support!

1 Like

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.