Empty results page after per-page selector change in FilamentPHP table

Expected Pagination Behavior

In standard FilamentPHP table implementations, changing the per-page selector is expected to reset the active page to one. Because Filament leverages Livewire's WithPagination trait, the table component must explicitly trigger a page reset when the per-page limit changes to ensure the resulting Eloquent offset does not exceed the total record count.

Why Empty Results Occur

An empty results page occurs when the active page number is preserved while the per-page value is modified. This creates a mathematical mismatch between the requested offset and the available data.

Example Scenario:

• Total Records: 50
• Current State: Page 3, Per-Page 10 (Offset = 20)
• Action: Change Per-Page to 25
• Result: If the page remains 3, the new Offset becomes 50 ((3-1) * 25). Since the total records are 50, the query requests records starting at index 50, returning an empty set.

Likely Causes and Versioning

While modern Filament versions handle this reset automatically, you may encounter this behavior under the following conditions:

• Custom Pagination Overrides: If the table component or a custom pagination class overrides the default Livewire pagination hooks, the resetPage() call may be bypassed.
• Legacy Versions: Older versions of the Filament/Livewire ecosystem may have lacked the automatic state synchronization between the per-page selector and the page index.
• State Desynchronization: If the page number is being manually managed in the component state rather than relying on the WithPagination trait's internal logic.

Verification Steps

To diagnose if your environment is failing to reset the page, perform the following test:

1. Ensure your table has a sufficient record count (e.g., 50+).
2. Navigate to page 2 or 3.
3. Increase the per-page selector to the maximum available value.
4. Observe the URL or component state: if the page number remains 2 or 3 and the table is empty, the reset logic is missing.

Diagnostic Detail Needed: Are you using a custom pagination class or have you overridden the paginateTable() method in your resource?