Update best practices for Scheduled View queries #6115
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
Clarified the importance of using a timeslice operator in Scheduled View queries, including details on default behavior and implications for data backfilling.
JV0812
requested review from
amee-sumo,
jpipkin1,
kimsauce and
mafsumo
as code owners
jpipkin1
reviewed
Dec 15, 2025
| * **Always use an [aggregate](/docs/search/search-query-language/group-aggregate-operators) operator**. This will allow you to avoid duplicating data. | ||
| * **Always run an aggregation by a [timeslice](/docs/search/search-query-language/search-operators/timeslice) operator.** If you do not, [Receipt Time](/docs/search/get-started-with-search/build-search/use-receipt-time) will be used. | ||
|
|
||
| * **Always run an aggregation with a [timeslice](/docs/search/search-query-language/search-operators/timeslice) operator.** If you do not specify one, [Receipt Time](/docs/search/get-started-with-search/build-search/use-receipt-time) will be used by default. Without timeslice or any other timestamp related field, Scheduled Views will not backfill the data. Instead it will begin populating data from the date the Scheduled View is created. |
Collaborator
There was a problem hiding this comment.
Suggested change
| * **Always run an aggregation with a [timeslice](/docs/search/search-query-language/search-operators/timeslice) operator.** If you do not specify one, [Receipt Time](/docs/search/get-started-with-search/build-search/use-receipt-time) will be used by default. Without timeslice or any other timestamp related field, Scheduled Views will not backfill the data. Instead it will begin populating data from the date the Scheduled View is created. | |
| * **Always run an aggregation with a [timeslice](/docs/search/search-query-language/search-operators/timeslice) operator.** If you do not specify one, [Receipt Time](/docs/search/get-started-with-search/build-search/use-receipt-time) will be used by default. Without `timeslice` or any other timestamp related field, Scheduled Views will not backfill the data. Instead it will begin populating data from the date the Scheduled View is created. |
jpipkin1
approved these changes
Dec 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose of this pull request
This pull request is to add information about using a timeslice operator in Scheduled View queries, including details on default behavior and implications for data backfilling.
Select the type of change
Ticket (if applicable)
Need timeslice operator in aggregation to backfill the data for schedule views