Long wait time before response to voice prompt

Summary / Zusammenfassung

Partly still existing problem, see time stamps in screenshot

Event on the regular servers

Steps to Reproduce / Schritte zur Reproduktion

  1. Go to ‘…’ / Gehe zu ‘…’
  2. Click on ‘…’ / Klicke auf ‘…’
  3. Scroll down to ‘…’ / Scrolle nach unten zu ‘…’
  4. See error / Fehler sichtbar

Expected Behavior / Erwartetes Verhalten

Actual Behavior / Tatsächliches Verhalten

Impact on Usage / Auswirkung auf die Nutzung

Minor: Small / cosmetic impact. / Kleiner / kosmetischer Einfluss.
Moderate: It disrupts some workflows. / Beeinträchtigt einige Arbeitsabläufe.
Critical: I can’t use the platform at all. / Die Plattform ist nicht nutzbar.

Screenshots or Logs / Screenshots oder Protokolle

image

Was time shifted into a different tempo than normal?

I’m afraid I can’t say that now.

Is the problem still occurring since this morning?

It happened to me again too. PF sends request to speak → speaks immediately → sends request to speak again a short time later → does not speak → sends request to speak again → responds approximately 1 minute later

EDIT: The sim speed was changed again and again. This causes the timestamp in the radio to be real time, but the sim time is already quite a bit further ahead

Yes, this has now been identified as the cause of the problem. Our internal tests did not include time jumps, which is why the error was not caught.

1 Like

I’m still having the problem. A time jump was actually made in the session (at some point). Communication worked in general, but as soon as larger operations are running, it stops working

I also often experience delays in the dispatch implementing the speech request from the rescue vehicle… but the NEF always press the normal speech request first and then the urgent speech request to get through

I wasn’t able to identify any issues with time jumps after today’s patch.

@danielschwarz just noticed: on https://stage.sim-dispatcher.com/de-DE a different version is displayed at the bottom than in the session window. The former shows 4.8.104-rc.1, the latter 4.8.106-rc.1