You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a monitored transit trip is reported as delayed by OTP, and the first trip delay notification is sent by OTP middleware, the new "reference" time for the trip is the delayed departure/arrival time. Subsequent trip delays and notifications are calculated based on the new "reference" time. If a transit vehicle recovers from a delay and the change is less than the defined variance, then no notification is sent, and the user could miss their transit trip.
Expected behavior
Notifications should be sent if a transit vehicle recovers from a delay.
Steps to reproduce the problem
TBD
Any special notes on configuration used
NA
Version of otp-middleware and/or OpenTripPlanner if applicable (exact commit hash or branch name)
Latest dev branch.
The text was updated successfully, but these errors were encountered:
Observed behavior
When a monitored transit trip is reported as delayed by OTP, and the first trip delay notification is sent by OTP middleware, the new "reference" time for the trip is the delayed departure/arrival time. Subsequent trip delays and notifications are calculated based on the new "reference" time. If a transit vehicle recovers from a delay and the change is less than the defined variance, then no notification is sent, and the user could miss their transit trip.
Expected behavior
Notifications should be sent if a transit vehicle recovers from a delay.
Steps to reproduce the problem
TBD
Any special notes on configuration used
NA
Version of otp-middleware and/or OpenTripPlanner if applicable (exact commit hash or branch name)
Latest dev branch.
The text was updated successfully, but these errors were encountered: