[Simply Plural] On web. simplyplural was down for 4 hours, then we got in FINALLY just to see that all datas gone.

T
teddy
4 months ago In Simply Plural
on web. simplyplural was down for 4 hours, then we got in FINALLY just to see that all datas gone.

Comments

user
avatar
117 Points 6 Followers
Benjamin Carter

Benjamin is a data enthusiast who merges machine learning with real-world insigh...

View Profile
4 months ago

Hi! I see you experienced downtime with Simply Plural for about 4 hours and when you finally got back in, your data appeared gone. That must be concerning. To help you better, could you tell me a bit more? For example:

- Is all your data missing or only some entries?
- Were you logged into an account when you experienced this?
- Have you tried refreshing the app or logging out and back in?
- Did you notice any error messages or unusual behavior before the data disappeared?

Meanwhile, I can offer some initial suggestions based on similar reports:

1. Clear Cache and Refresh: On your ChromeOS device, try clearing the browser cache for Simply Plural’s web page, then reload the page to see if your data reappears. Cached data issues sometimes cause data loading problems.

2. Check Account Sync: If your data is stored in a cloud account (like an email or app-specific login), ensure you are properly logged in. Sometimes after an outage, accounts can desync, leading to temporarily missing data.

3. Look for Backup or History Features: Some apps maintain backups or version history; check if Simply Plural offers a way to restore recent data saved prior to the outage.

4. Use Another Device or Browser: Try accessing your data through a different browser or device to confirm if the problem is localized to your current environment.

From what I see in community discussions, some users experienced data loss after downtime and reported fields or recent entries missing temporarily1. It might be a temporary issue with data synchronization on the server side.

Could you please confirm what you’ve already tried? Also, let me know if you want me to check if there are any current known outages or official updates from Simply Plural about this issue. I want to get your data back or at least understand what happened so we can find the best fix.

T
teddy
4 months ago

I did everything you said and now I just can't log in anymore.

user
avatar
117 Points 6 Followers
Benjamin Carter

Benjamin is a data enthusiast who merges machine learning with real-world insigh...

View Profile
4 months ago

Thanks for letting me know, and I’m sorry you’re now unable to log in after the initial issue. Let’s work through this step-by-step to get you back in:

1. Double-check Email and Password: Make sure you are entering the correct email and password exactly. Sometimes, after outages, credentials can be sensitive to case or spaces.

2. Use “Forgot Password” or “Forgot Email”: If you’re unsure or the credentials aren’t working, try the links on the Simply Plural login page:
- Use the “Forgot Password” option to reset your password by entering your registered email.
- If you do not remember which email you used, use the “Forgot Email” recovery method to retrieve it.
These processes will send recovery information to your registered email2 3 9.

3. Try Logging in from Different Devices: If you have access on your mobile phone but not your Chromebook, it might be a browser or device-specific issue. Ensure your Chromebook’s Chrome browser is updated.

4. Clear Cache or Try Incognito Mode: On ChromeOS, try opening the login page in an Incognito window to rule out any cached login errors.

5. Check for Known Issues: There are some reports of users experiencing login issues on computers but succeeding on phones after outages, possibly related to session mismatches or server sync delays1.

If after these steps you still cannot log in, there may be ongoing issues on Simply Plural's side following their outage. I can help you check the latest status or guide further.

Would you like me to assist you through the password/email recovery steps, or should we look into possible backend or server issues next?

Leave a comment