🎬 Gotofilm

v643

Find films you want, at the London cinemas you can get to fastest.

Set the hours first, then the minutes.

Car drop-off

Prefer to drive to your local station? Choose your drop-off and driving time.
⚠️ Debug (0)

For developer use only.

Timetable and search checks

No search issues have been recorded.

Cache
  1. Enabled — Tube/DLR/Elizabeth/Overground timetable. Update frequency: checked and refreshed daily at 06:00 Europe/London, with missed work caught up at server startup. Last updated 31 Oct at 06:00. TfL source age at the latest check: 5.4 days.
  2. Enabled — Bus timetable. Update frequency: checked and refreshed daily at 06:00 Europe/London, with missed work caught up at server startup. Last updated 31 Oct at 06:00. TfL source age at the latest check: 4.8 days.
  3. Enabled — Cinema and showtime listings. Update frequency: daily at 06:00 Europe/London; only the current and previous successful Google Cloud snapshots are retained. Last updated 31 Oct at 06:23. snapshot age when last checked: 4.1 hours.
  4. Enabled — Film metadata. Update frequency: checked after the daily 06:00 listings refresh; successful records are retained for 30 days and unavailable records for 24 hours; expired records are swept and at most 5,000 entries are retained. Last updated 31 Oct at 10:30.
  5. Enabled — In-memory listings search index. Update frequency: rebuilt after the daily listings refresh and cleared on server restart. Last updated 31 Oct at 06:23.
  6. Enabled — Cinema-to-Tube/DLR/Elizabeth/Overground walking records. Update frequency: new, missing and expired records are filled daily at 06:00 Europe/London and after server startup; all records are fully refreshed every 14 days after the current Tube/DLR/Elizabeth/Overground timetable is activated; obsolete records are pruned. Last updated 15 Oct at 06:16. Last checked 31 Oct at 10:31. Age of the latest full refresh: 16.8 days. Latest full refresh failed; the previous complete cache was retained. 22 cinema access record(s) failed; obsolete records were retained.
  7. Enabled — Cinema-to-Bus-stop walking records. Update frequency: new, missing and expired records are filled daily at 06:00 Europe/London and after server startup; measured records are retained for 90 days and definite all-stop no-route results for 24 hours; a complete daily pass removes cinemas no longer listed. Last updated 31 Oct at 10:31. 123 stored records loaded into memory; 0 missing or expired records left lazy; startup warming makes no walking API requests.
  8. Enabled — Shared TfL Line Status and StopPoint disruption snapshots. Update frequency: Tube-family current conditions are refreshed every 90 seconds; Tube-family and Bus searches reuse current-date results for up to two minutes, future-date results for 30 minutes, and at most eight service dates remain in memory per mode. Last updated 31 Oct at 23:33. The displayed refresh time is for the background Tube-family snapshot. Bus snapshots are populated on demand and then shared briefly between Bus searches.
  9. Enabled — Prepared local routing tables. Update frequency: at server startup, during the daily 06:00 maintenance window, after a Tube/DLR/Elizabeth/Overground timetable refresh, and lazily for any date not already prepared; at most seven service dates remain in memory. Last updated 31 Oct at 10:30. 1 of 7 selectable dates prepared in this server process.
  10. Enabled — Prepared Bus routing tables. Update frequency: today at server startup and daily maintenance, and a future day when the user selects it; at most two service dates remain in memory. Last updated 31 Oct at 10:30. 1 of 7 selectable dates prepared in this server process; Bus readiness is separate from Tube readiness.
  11. Enabled — Temporary result pages. Update frequency: whenever a search result changes; pages remain restorable from Google Cloud until 30 minutes after the user's last activity, while each server keeps at most 100 in RAM. Last updated 1 Jan at 01:00. 0 pages currently loaded in this server's memory; other live shared pages are loaded on demand.
  12. Disabled — new-location station and stop walks. Update frequency if re-enabled: on a cache miss, with each coordinate-pair result retained for up to 90 days.
  13. Disabled — direct origin-to-cinema walks. Update frequency if re-enabled: on a cache miss, with each result retained for up to 90 days.
  14. Disabled — exact TfL Journey Planner results. Update frequency if re-enabled: on a cache miss, with each result retained for two minutes.
  15. Disabled — recently cleared serious disruptions. Update frequency if re-enabled: whenever the TfL status snapshot changes, with cleared items retained for 15 minutes.
  16. Disabled — resolved TfL station identities. Update frequency if re-enabled: on a cache miss, retained until server restart.
  17. Disabled — location autocomplete suggestions. Update frequency if re-enabled: on a cache miss, with each result retained for ten minutes.
Buffers
  1. Tube/DLR/Elizabeth/Overground entry: add 2 minutes after the measured walk to the departure station to allow time to reach the platform.
  2. Tube/DLR/Elizabeth/Overground changes: allow 4 minutes for each interchange.
  3. Tube/DLR/Elizabeth/Overground exit: add 2 minutes before the measured walk from the destination station to the cinema.
Misc
  1. TfL Journey Planner checks run only when users press a row’s Check with TfL button, one journey at a time. General disruption feeds and definite local closure checks still run automatically.
  2. Cinemas without a usable station in the compiled local network are excluded.
  3. Cinema/showtime journeys that the compiled local timetable cannot construct are excluded instead of falling back to TfL.
  4. Startup note: Search waits while the compiled TfL timetable, today’s routing tables and existing cinema access records load into memory. The ‘Server starting…’ modal then disappears automatically; a future selected day is prepared when the user selects it and still has a safe lazy path. This preparation is separate from the disabled data caches listed above.
  5. TfL’s external cache: a new or changed journey request may be much slower than a recently repeated one. We cannot control this, so first searches can take longer even when our own caching is disabled.
  6. Journey times are calculated from the downloaded TfL timetable rather than TfL’s live Journey Planner, so there may be discrepancies between the displayed times, the live planner and actual travel.
  7. Autocomplete selection note: the selected postcode, station or address carries coordinates obtained by the same location services used to populate the menu. This is short-lived form selection state, not a cache. Automated or command-line searches resolve an exact location through those same services and never request a dummy journey merely to obtain coordinates.
  8. Timetable refresh history, health and validated timetable artefacts are shared through Google Cloud Storage. Local timetable files are replaceable working copies.
  9. Completed and failed search diagnostics are stored as separate records in Google Cloud Storage for retrospective debugging.
  10. External API timeouts, network and HTTP errors, rate limits, malformed replies, and slow calls are stored as separate redacted records in Google Cloud Storage.
  11. The browser stores the selected sort order and live-result display state for the current browser session; this does not cache API responses.