Usage records datetime picker choosing wrong enddate with Local Timezone enabled

[MitchDrage]

problem

When 'Use local timezone' is disabled in my client profile, and with the picker dates selected as 2026-07-01 (start of this month) through to today - 2026-07-10, the follow query string is passed in browser call:
page=1&pagesize=20&startdate=2026-07-01+00:00:00&enddate=2026-07-10+23:59:59&command=listUsageRecords&response=json&sessionkey=xyz

However when 'Use local timezone; is enabled, the enddate is mangled and appears to be showing as 24 hours after the start date.
page=1&pagesize=20&startdate=2026-06-30+14:00:00&enddate=2026-07-01+13:59:59&command=listUsageRecords&response=json&sessionkey=xyz

This happens regardless of the dates chosen, i.e. not just a start of the month thing.
I woudl also have expected - even if the enddate is set to 24 hours after the startdate (ignoring the selected datetime range), that it would still have returned results.

My local timezone is Australia/Melbourne, and I've found this to happen when the usage server settings (usage.aggregation.timezone and usage.execution.timezone) are set to UTC as well as Australia/Melbourne.

So to be clear - a workaround exists as disabling local timezone returns the correct results.

versions

ACS 4.22.1.0

The steps to reproduce the bug

1. Confirm that Use Local Timezone is disabled.
2. Execute a Show Usage Records query in the Tools > Usage page
3. The query returns records and the datetime in the query is correct.
4. Enable Use Local Timezone and execute Show Usage Records with the same or a different datetime range.
5. The query returns an empty result ({"listusagerecordsresponse":{}}), and the query has the enddate set to 24 horus after the start date.

What to do about it?

No response

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!