401 no token provided on VKO

[infoseekAI]

Any ideas what's up with these airports?

note that in the google flights UX there is an additional widget shown, could that mess with the parser?

Limited flight results
Google Flights has limited flight results on this route

Logs:

=== Searching route: VKO -> PVG ===

{'from_code': 'VKO', 'to_code': 'PVG', 'departure_date': '2026-03-25', 'return_date': '2026-03-31', 'max_duration_hrs': '30', 'max_stops': '2', 'flight_class': 'economy', 'adults': '1', 'children': '0', 'error_details': 'Error processing route VKO -> PVG: 401 Result: {"error":"no token provided"}\n'}

=== Searching route: VKO -> SHA ===
{'from_code': 'VKO', 'to_code': 'SHA', 'departure_date': '2026-03-25', 'return_date': '2026-03-31', 'max_duration_hrs': '30', 'max_stops': '2', 'flight_class': 'economy', 'adults': '1', 'children': '0', 'error_details': 'Error processing route VKO -> SHA: 401 Result: {"error":"no token provided"}\n'}

[dosubot[bot]]

The "401 no token provided" error usually means Google Flights isn't returning the required authentication token for your VKO routes. This can happen if Google limits results for certain airports or routes, or if the UI changes (like the "Limited flight results" widget) interfere with how the scraper extracts tokens or parses the page.

Recent reports and code show that these UI changes can break token extraction and parsing, leading to 401 errors, especially when Google displays special widgets or restricts data for specific routes (source). The parser relies on specific HTML structure, so new widgets or limited results messages can disrupt it.

A practical workaround is to use the Playwright-based fetch modes (fetch_mode="local" or mode="force-fallback"), which automate a real browser to fetch and parse the page HTML. This approach can bypass token-related issues and has been reported to work for problematic routes where standard scraping fails (source, source, source).

If you haven't already, try switching to Playwright mode for these VKO routes. If the issue persists, it's likely due to backend limitations or further UI changes by Google that restrict access to flight data for these airports.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}