Problem

Development teams often work across different geographical locations and time zones, while the OutSystems environment is typically configured with a different server time zone (for example, UTC or a customer-specific time zone).

When reviewing timers, scheduler executions, logs, deployments, or other time-based activities in Service Center, users must manually calculate the current server date and time using external tools or time zone converters. This is inconvenient and can lead to confusion when validating whether a timer has executed or when correlating log timestamps.

Proposed Solution

Display the current server date and time prominently within Service Center (for example, in the header or footer). The display should automatically reflect the environment's configured time zone and optionally show the time zone abbreviation.

Example:

Server Date & Time: 10 Jul 2026, 14:35:42 UTC

Benefits

• Eliminates the need to manually convert server time across different time zones.
• Makes it easier to verify timer executions and scheduler runs.
• Simplifies troubleshooting, deployments, and log analysis.
• Reduces errors caused by time zone differences.
• Improves productivity for developers, architects, tech leads, and support teams working across multiple regions.

This small enhancement would provide immediate visibility into the server's current date and time, making Service Center more efficient for day-to-day monitoring and troubleshooting.