Skip to main content

Clear Cache and Hard Reload to Resolve Errors

If you’re seeing error messages on Web or Mobile, doing a hard reload or clearing your cache may help resolve the issue.

Written by Angelene Rosario

Clearing your cache fixes browser-side display and loading issues only. If you are seeing a server error (HTTP 500, timeout, or a platform-wide outage message), PDF download failures, records not appearing in search, or fields that are locked or greyed out — these are not cache issues. Jump to the relevant section below for the right fix.

For Web App Users

Before clearing your browser cache, try these quick steps first. They are faster, less disruptive, and often enough to fix temporary loading or display issues.

Refreshing the page or doing a hard reload forces your browser to pull in the latest version of BuildOps instead of relying on older saved files. Signing out and back in can also refresh your session and clear temporary issues related to login or loading.

If the issue continues after these steps, clear your browser cache to remove older stored files that may be causing conflicts.

Is your issue actually a cache problem?

Cache clearing resolves issues caused by your browser holding on to outdated files. It will NOT fix:

  • Server errors or platform outages — if other users are also affected, the issue is on BuildOps' side. Check with your team first before clearing cache.

  • PDF or file download failures — if files download without a .pdf extension or fail entirely across multiple browsers, this is a server-side file processing issue, not a cache problem.

  • Records not appearing in search or dropdowns — newly created records can take a few minutes to index. If a record is missing after several minutes, contact BuildOps Support.

  • Locked or greyed-out fields — these reflect your role permissions or the record's current status, not cached data.

  • Form validation errors that persist — if required fields are flagged even after correct input, this is a data or workflow state issue, not a cache issue.

If your issue matches one of the above, skip to the relevant section below. If you are unsure, try a hard reload first — it is faster and less disruptive than a full cache clear.

Steps to do a Hard Reload

  1. Refresh the page.

  2. If you’re using Google Chrome, do a hard reload:

    • Windows: Ctrl + Shift + R

    • Mac: Command + Shift + R

If you’re still running into errors after logging out and back in, clearing your cache may help.

Steps to Clear Cache

For Google Chrome

  1. Open Chrome.

  2. Click the three dots (⋮) in the top-right corner.

  3. Go to Settings → Privacy and security.

  4. Select Clear browsing data.

  5. Set the Time range to All time.

  6. Make sure Passwords and Autofill form data are unchecked (so they won’t be deleted).

  7. Click Clear data.

For Safari (Mac)

  1. In the top menu bar, click Safari.

  2. Select Settings (or Preferences on older macOS versions).

  3. Go to the Privacy tab.

  4. Click Manage Website Data…

  5. Click Remove All, then Confirm.

Tip: A quick shortcut on most browsers is Ctrl + Shift + Delete (Windows) or Command + Shift + Delete (Mac). Another useful technique is adjusting the browser’s zoom level, accessible via the browser’s menu, to ensure optimal display of elements.

Steps to Clear Cache in Firefox

  1. Click the menu icon (☰) in the top-right corner.

  2. Go to Settings → Privacy & Security.

  3. Under Cookies and Site Data, click Clear Data.

  4. Check Cached Web Content and click Clear.

Steps to Clear Cache in Microsoft Edge

  1. Click the three dots (…) in the top-right corner.

  2. Go to Settings → Privacy, search, and services.

  3. Under Clear browsing data, click Choose what to clear.

  4. Set Time range to All time, check Cached images and files, then click Clear now.

For Mobile App Users

Only do this when you have a stable internet connection and after any important work has fully synced.

  1. Tap the menu icon at the top right of your screen.

  2. Select Clear Cache & Restart.

  3. The app will automatically refresh and reopen.

When cache clearing does not fix the issue

Server errors and platform outages

If you see an HTTP 500 error, a timeout, or a message that the service is unavailable, this is a server-side issue that cache clearing cannot resolve.

  • Check whether other users on your team are seeing the same error — if so, it is likely a platform-side issue.

  • Wait a few minutes and try again.

  • If the error persists across users and browsers, contact BuildOps Support and include the exact error message and the time it started.

Records not appearing in search or dropdowns

Newly created or updated records (customers, properties, items) can take a few minutes to appear in search results and dropdowns after being saved. This is a backend indexing delay, not a cache issue.

  • Wait 2–5 minutes, then search again.

  • If the record is still missing after 10 minutes, try navigating directly to the record to confirm it was saved correctly.

  • If the record exists but does not appear in search after 15 minutes, contact BuildOps Support.

Locked or greyed-out fields

If a field or button is greyed out or unavailable, the cause is either the record's current status or your role permissions — not cached data. Cache clearing will not unlock these.

  • Check the record's current status (e.g. Posted, Approved, Closed). Some actions are only available at specific statuses.

  • If you believe you should have access to an action but do not, contact your BuildOps administrator to review your role permissions.

Mobile app issues that persist after clearing cache

If problems on the mobile app continue after clearing cache and restarting — such as attachments not syncing, signatures not saving, or Smart Recap errors — try these additional steps:

  • Ensure you are on a stable Wi-Fi or cellular connection before syncing.

  • Check that you are running the latest version of the BuildOps app — outdated app versions can cause persistent errors.

  • If the issue continues after updating the app, contact BuildOps Support with your device type, OS version, and app version.

How to Find and Verify Your App Version

On iOS Devices

  1. Open the App Store on your device.

  2. Search for the BuildOps app.

  3. The app version will be displayed in the app details section.

On Android Devices

  1. Open the Google Play Store on your device.

  2. Search for the BuildOps app.

  3. The app version will be displayed in the app details section. Alternatively, within the BuildOps app:

  4. Tap the three lines (menu icon) in the upper-right corner.

  5. Select App Version. This will take you to the Session Details page, where you can view the app version and session details.

Related Articles
Did this answer your question?