Booking not appearing in /admin/bookings listing but found via filter[search]

Bug Reports
1

We have a confirmed upcoming booking (ID: 731, code: 24yckaoyr) that does not appear in the /admin/bookings listing endpoint, but is returned when searching directly via filter[search]=24yckaoyr.

Company : institutalgovita

Steps to reproduce:

  1. GET /admin/bookings?filter[upcoming_only]=1&page=1&on_page=100 → booking 731 not present

  2. GET /admin/bookings?filter[upcoming_only]=1 (no status filter) → booking 731 not present

  3. GET /admin/bookings?filter[search]=24yckaoyr → booking 731 returned correctly

Booking details:

  • ID: 731

  • Status: confirmed / is_confirmed: true

  • start_datetime: 2026-03-13 11:45:00 (upcoming)

  • record_date: 2026-03-11 20:13:30 (created yesterday)

  • user_status_id: 3

Observation:
Another booking (ID: 522) with identical user_status_id: 3 and null invoice does appear in the regular listing. The only notable difference is that booking 731 was created more recently (record_date yesterday vs. 2 weeks ago for booking 522).

Question:
Is there a caching mechanism in the /admin/bookings listing that delays newly created bookings from appearing? If so, what is the cache TTL, and is there a way to force a refresh or bypass it?

3

Hi, we have no cache on that endpoint, and “upcoming_only” filter is straightforward - it takes all bookings with date_start >= current datetime (in company time)

Did that booking appear in the response later?

4

No using the rest api the problem persisted, i switched to the RPC api ‘getBookings’ and it was solved

5

I’ve checked your configuration and that booking should be returned properly. Could there be a problem with pagination? I am currently out of ideas what else could go wrong