Check realtime mode in remote clock interceptor (#6985)

* Revert Date.now() purge change Check that the request is using realtime before using the remote-clock start and end timestamps for telemetry requests * docs: clarify comment --------- Co-authored-by: Jesse Mazzella <[email protected]>
nasa · Oct 3, 2023 · ce59c0f · ce59c0f
1 parent d53d8d5
commit ce59c0f
Showing 1 changed file with 10 additions and 4 deletions.
diff --git a/src/plugins/remoteClock/requestInterceptor.js b/src/plugins/remoteClock/requestInterceptor.js
@@ -31,10 +31,16 @@ function remoteClockRequestInterceptor(openmct, _remoteClockIdentifier, waitForB
       return activeClock?.key === 'remote-clock' && !remoteClockLoaded;
     },
     invoke: async (request) => {
-      const { start, end } = await waitForBounds();
-      remoteClockLoaded = true;
-      request.start = start;
-      request.end = end;
+      const timeContext = request?.timeContext ?? openmct.time;
+
+      // Wait for initial bounds if the request is for real-time data.
+      // Otherwise, use the bounds provided by the request.
+      if (timeContext.isRealTime()) {
+        const { start, end } = await waitForBounds();
+        remoteClockLoaded = true;
+        request.start = start;
+        request.end = end;
+      }
 
       return request;
     }