5 ms·
Hi Guys. I'm with Team Linkwok. We regret the issue that you guys faced. It was because of our MongoDB service provider. Our oplog instance was offline. We have
by scorpwarp23 12y ago
Hi Guys. I'm with Team Linkwok. We regret the issue that you guys faced. It was because of our MongoDB service provider. Our oplog instance was offline. We have subsequently added a fix for this. The internal server error should not appear anymore. Thanks for your patience. As for the feedback you'll have given us, many thanks, we shall take your points into consideration.
- scorpwarp23 12y agoMany of you with the app running might face a reload as the page hot-code reloads so that you have the latest version of the App.