SharePoint Document Issues

Fix SharePoint Online Failed to Load Current Time Zone Error

Steven ParkerSteven Parker Nov 2, 2026 868 views

Question details

Users are encountering a time zone loading error when attempting to create or modify SharePoint list items that rely on calculated date values.

How to Fix SharePoint Online 'Failed to Load Current Time Zone' Error
Product
SharePoint Online
Device & OS
not provided
Scenario
Creating or modifying SharePoint list items that use calculated date formulas, such as NOW()+70.
Observed behavior
SharePoint Online displays a 'Failed to Load Current Time Zone' error message and prevents the list item from saving correctly.
Before you start

Ensure you have exact documentation of the calculated column formula causing the issue and check if multiple users in your tenant are experiencing the same error.

Solution 1Recommended

Report the Issue to Microsoft Developer Support

Because this error affects SharePoint Online backend calculations and typically impacts multiple users, it must be addressed by Microsoft's engineering team.

Time zone errors tied to calculated columns like NOW() or TODAY() are often symptoms of tenant-wide backend desynchronization in SharePoint Online.

End users cannot fix this locally. The issue must be escalated through proper administrative channels with specific tenant details to trace the server anomaly.

1
Gather affected list details

Note down the exact URL of the affected SharePoint list, the specific calculated-column formula being used (e.g., NOW()+70), and the exact time the error started occurring.

2
Access Microsoft Tech Community or Q&A

Navigate to the Microsoft Tech Community or Microsoft Q&A forums, which are monitored by Microsoft engineers and developer support teams.

3
Submit a detailed support request

Create a new post including your tenant details, the formula, and the scope of affected users so Microsoft can investigate the backend calculation service.

Report the Issue to Microsoft Developer Support
For End Users: If you are an end user without administrator access, contact your organization's IT helpdesk so they can open an official support ticket with Microsoft from the Microsoft 365 Admin Center.
Free Microsoft Office alternative

Switch to WPS Office for Seamless Document Management

While dealing with complex SharePoint backend server errors, ensure your team's document productivity remains uninterrupted. WPS Office is a lightweight, fully compatible alternative to Microsoft Office that makes managing documents, spreadsheets, and presentations hassle-free.

  1. 1. Download the installer: Visit the official WPS website and download the free WPS Office installer for your operating system.
  2. 2. Install WPS Office: Run the downloaded file and follow the quick setup wizard to install the suite on your computer.
  3. 3. Open Office files seamlessly: Launch WPS Office and directly open your existing Microsoft Word, Excel, and PowerPoint documents.
Fully compatible with Microsoft Office formats including .docx, .xlsx, and .pptx.Lightweight software with blazing fast startup times and minimal system requirements.Familiar user interface that requires zero learning curve for Office users.Built-in cloud storage to securely manage files without relying on complex SharePoint lists.
microsoft office alternative - wps office

Frequently Asked Questions

What causes the 'Failed to Load Current Time Zone' error in SharePoint?

This error is typically caused by backend server desynchronization in SharePoint Online when processing volatile functions like NOW() or TODAY() inside calculated columns.

Can I fix the SharePoint time zone calculation error myself?

Generally, no. Because it is a server-side issue that often impacts an entire tenant, it requires intervention from IT administrators or Microsoft Developer Support to resolve.

Are NOW() and TODAY() officially supported in SharePoint calculated columns?

While commonly used, volatile functions like NOW() and TODAY() are not officially supported in calculated columns because they only update when the item is explicitly modified, which can lead to calculation inconsistencies and time zone glitches.