Cannot read properties of undefined (reading 'ElapsedMilliseconds')

[c0shea]

Describe the bug Seq returns the error "Cannot read properties of undefined (reading 'ElapsedMilliseconds')" for a long-running query.

To Reproduce Steps to reproduce the behavior:

1. Run a long-running query, such as select RequestBody from stream limit 100000000000 over a 3 day span. It's expected to return 40,000 or so rows of JSON payloads.
2. After a minute or so, it returns the error message

Expected behavior A clearer message that my user timeout period has elapsed. My profile is set to 2,000 seconds and that wasn't respected as the error returned in less than two minutes instead of 33 minutes.

Screenshots

Environment (please complete the following information):

• OS: Windows
• Browser: Edge
• Seq Version: 2024.3.11510
• Using Docker? No

[liammclennan]

Hi @c0shea

When you get this error is there a stack trace (or any more detail) in the browser's developer console?

[c0shea]

Yes, it writes this to the console:

TypeError: Cannot read properties of undefined (reading 'ElapsedMilliseconds')
    at api.data.inSignal.then.cancelLastRequest (main-LSJBemFd.js:18:196948)
    at angular-DvxoCOxF.js:141:454
    at m.$digest (angular-DvxoCOxF.js:153:67)
    at m.$apply (angular-DvxoCOxF.js:156:484)
    at k (angular-DvxoCOxF.js:107:445)
    at v (angular-DvxoCOxF.js:113:40)
    at y.onload (angular-DvxoCOxF.js:113:464) 'Possibly unhandled rejection: {}'

The main-LSJBemFd.js file pointed to this line:

[liammclennan]

That's brilliant. Thank you. We'll get this fixed.

[liammclennan]

this is fixed for the next release. Thanks for the report @c0shea !