1. Refresh the Browser
Click the refresh icon (a circular arrow) in the address bar. While this method can help, it may not always fully update the application to the latest version.
2. Log out of Castaway and log back in
Sometimes, logging out of your Castaway Cloud session and then logging back in can refresh the session and reflect any updates.
3. Restart the Browser
Close all browser windows and reopen Microsoft Edge. Navigate back to https://cloudcastaway.com to see if the update is now reflected.
4. Restart your computer
If the updates still don’t appear, try restarting your computer. This can resolve any lingering issues with browser or system caches that might be preventing you from seeing the latest changes.
5. Clear caches and cookies
To clear the cache for just Castaway cloud site without affecting the entire browser, follow these steps based on the browser you’re using:
Google Chrome
- while in our Castaway cloud product site https://cloudcastaway.com click on View Site Information icon in the address bar.
- Select Site settings
- Under Usage, click Delete data
Microsoft Edge
- In Edge browser, click the Ellipsis icon (three dots) in the upper right corner.
- Select Settings from the dropdown menu and type edge://settings/siteData in Edge URL in the address bar.
- Type Cloudcastaway in the search box. Alternatively you can find the website by scrolling the list.
- Click on the trash icon next to cloudcastaway site
Firefox
- while in our Castaway cloud product site https://cloudcastaway.com click on View Site Information, or padlock icon in the address bar.
- Select Clear cookies and site data
- Confirm by clicking Remove
If you’ve tried the above steps and still can't get the latest updates in Castaway Cloud, please reach out to your IT staff for further assistance, as this is not a usual occurrence.
Alternatively, you can try accessing Castaway Cloud using a different browser like Chrome, Edge, or Firefox. Another option is to open Castaway in a private browsing mode, such as Incognito, which doesn't use cache data and may help confirm if the issue is cache-related.