Skip to content

Failed-message list cannot be sorted by "Time of failure" — silently falls back to "Time sent"#5479

Merged
ramonsmits merged 2 commits into
release-6.14from
fix/failed-messages-sort-by-time-of-failure-6.14
May 19, 2026
Merged

Failed-message list cannot be sorted by "Time of failure" — silently falls back to "Time sent"#5479
ramonsmits merged 2 commits into
release-6.14from
fix/failed-messages-sort-by-time-of-failure-6.14

Conversation

@ramonsmits
Copy link
Copy Markdown
Member

The Primary instance global SortInfoModelBinder allowlist is missing the
'time_of_failure' and 'modified' sort keys. When ServicePulse requests the
failed-message list sorted by Time of failure (sort=time_of_failure), the
binder silently rewrites the token to 'time_sent', so the RavenDB layer —
which does support TimeOfFailure ordering — never sees it. The list ends up
ordered by Time sent regardless of the user's choice.

This test reproduces the defect at the binder level (RED).
Add the two missing sort keys to the Primary instance SortInfoModelBinder
allowlist so that sort=time_of_failure (and sort=modified) survive model
binding and reach the RavenDB query, which already maps them to the
TimeOfFailure / LastModified index fields.

Fixes the ServicePulse failed-message list ordering by 'Time of failure',
which previously fell back to 'Time sent'. (GREEN)
@ramonsmits ramonsmits requested a review from dvdstelt May 19, 2026 12:16
@ramonsmits ramonsmits added this to the 6.14.3 milestone May 19, 2026
@ramonsmits ramonsmits enabled auto-merge May 19, 2026 13:54
@ramonsmits ramonsmits merged commit e8e33d8 into release-6.14 May 19, 2026
95 of 121 checks passed
@ramonsmits ramonsmits deleted the fix/failed-messages-sort-by-time-of-failure-6.14 branch May 19, 2026 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants