Picking a custom date range in the webhook history filter excludes the end day the user selected.
filters.tsx converts the date input like this:
end: e.target.value ? new Date(e.target.value).toISOString() : ''
An <input type="date"> yields "2026-08-15", and new Date("2026-08-15") parses as UTC midnight at the start of that day. The API then applies $lte: new Date(end), so a range of Aug 1 to Aug 15 returns nothing from Aug 15 at all. For users in timezones behind UTC it also chops off the tail of Aug 14.
The end bound should be the end of the selected day (23:59:59.999), and arguably in the user's local timezone rather than UTC.
While in there: applyCustomRange in use-filters.ts doesn't validate that start is before end, so a reversed range applies silently and just shows an empty table.
Reactions are currently unavailable
Picking a custom date range in the webhook history filter excludes the end day the user selected.
filters.tsx converts the date input like this:
An <input type="date"> yields "2026-08-15", and new Date("2026-08-15") parses as UTC midnight at the start of that day. The API then applies $lte: new Date(end), so a range of Aug 1 to Aug 15 returns nothing from Aug 15 at all. For users in timezones behind UTC it also chops off the tail of Aug 14.
The end bound should be the end of the selected day (23:59:59.999), and arguably in the user's local timezone rather than UTC.
While in there: applyCustomRange in use-filters.ts doesn't validate that start is before end, so a reversed range applies silently and just shows an empty table.