🐛 Bug Report: Lines Not Found on Valid Dates

[razvardi77]

Summary

While testing the historical stop times view, several bus lines that are known to operate regularly (verified via Moovit or personal experience) return קו לא נמצא ("line not found") on specific dates, despite being available on nearby days.

This appears across multiple operators and lines, and in one case, the same line appears under a different operator on the same date, suggesting the issue may relate to operator/date mismatches, data gaps, or filtering logic.

---

Note: Line 15 with Electra Afikim (operatorId=25) demonstrates a critical bug, beyond the regular behavior observed in other cases

QA Test Matrix – Line Availability by Date and Operator

Date	Line Number	Operator Name	operatorId	Source Verified	Result	Conflict Detected?
1/5/25	45	Dan	5	Personal ride	Not Found	No
1/5/25	377	Metropoline	15	Moovit	Not Found	No
4/5/25	174	Egged	3	Personal ride	Found	No
5/5/25	45	Dan	5	Personal ride	Found	No
6/5/25	377	Metropoline	15	Moovit	Found	No
7/5/25	174	Egged	3	Personal ride	Not Found	No
1/5/25	10	Kavim	6	Moovit	Not Found	✅ Found in Moovit
4/5/25	10	Kavim	6	Moovit	Found	No

Line	Operator Name	operatorId	Dates (4–8.5.25)	Result	Notes
15	Electra Afikim	25	4–8.5.25	Not Found	❌ Missing entire workweek
451	Superbus	16	4–8.5.25	Not Found	❌ Critical – intercity line

---

174-Eged

45-Dan

377-Metrioiline

10-Kavim

15-Elecra Afikim

451-superbus

QA Observations

• Issues occur across different operators, not just one.
• Verified lines that work on one day disappear on another.
• In one case, line 15 appears under a different operator than expected.
• These issues do not correlate with Shabbat limitations:
  • Saturdays (Shabbat): Missing lines may be expected
  • Fridays: Lines should still appear, even with reduced service

---

Optional QA Insight

From the QA perspective, this may be due to:

• Partial GTFS data on some dates
• Lines are being assigned to the wrong operator in GTFS
• Filtering logic hides valid lines when no trips are found

These are only observations – technical investigation is up to the development team.

🔗 Example timeline URL

[NoamGaash]

Seems like this line is missing since 5.5.25:

Also seems like other lines are fine:

[krasnoff]

I would like to check out this issue please.

[krasnoff]

1. There are bus lines such as egged 147 which has no history of travel history while in other lines such as egged 950 we have travel history.

see for example the following API calls:
https://open-bus-stride-api.hasadna.org.il/gtfs_routes/list?limit=100&date_from=2025-06-03&date_to=2025-06-04&operator_refs=3&route_short_name=174

and an API which returns travel history:
https://open-bus-stride-api.hasadna.org.il/gtfs_routes/list?limit=100&date_from=2025-06-03&date_to=2025-06-04&operator_refs=3&route_short_name=950

2. I have discovered another problem: there is no debounce mechanism and as a result of that there are plenty of unnesseary API calls. For example: When we call for line 174 there are unnessesary calls to line 17 and line 1 as well.

Do you want me to build a debounce mechanism?

[NoamGaash]

@krasnoff debounce mechanism sounds like a great idea!
regarding the missing lines - we should investigate whether its a problem with the data, with the ETLs or with our API logic. that's great you have isolated an instance of the problem 👏

[krasnoff]

So I will start to work on the debounce mechanism if its fine with you