Bug Fix: TimeSeries Profile Instance Time Window #1544
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ere being compared against first and last of data time window instead of data point timestamp, causing 404 if specified time window was not inclusive of the complete profile instance data set. Updated previous/next integration test to have correct usage.
adamkorynta
approved these changes
Jan 22, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed bug with time series profile instance time window.
Start and end times were being compared against first timestamp and last timestamp of complete instance time window instead of individual data point timestamps, causing a not found error if the specified time window was not inclusive of the complete profile instance data set.
Updated integration test for previous/next parameters to have correct expected usages.
Issue discovered when documenting endpoint parameter usage for #1543