[One workflow] Event tab empty state in execute modal#272000
Open
yngrdyn wants to merge 2 commits into
Open
Conversation
yngrdyn
added
release_note:skip
botelastic
Bot
added
the
Team:One Workflow
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Module Count
Async chunks
History
cc @yngrdyn |
h88
approved these changes
Jun 1, 2026
Contributor
h88
left a comment
h88
left a comment
There was a problem hiding this comment.
LGTM.
For consideration: 1- higher test coverage (custom-KQL variant \etc...) 2- consider !isFetching in the empty state condition if you see a "flash"🪩 while refetching (reading the condition / haven't verified locally)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Relates to https://github.com/elastic/security-team/issues/16717.
Summary
When the event tab loads and the trigger-events search returns zero hits, show a dedicated empty state instead of an empty data grid. Copy is honest about time range and KQL (not “no events ever”), and points authors to practical next steps: widen the range, edit the query, open Manual, or fire a real event.
Motivation
Authors testing event-driven workflows often open the event tab before any rows appear in the default window (
now-15m→nowplus workflowtriggerIdscope). An empty grid with no explanation reads like a broken search. We need guidance that matches what the API actually returns: zero documents for the current time range and query—not a guarantee that the trigger has never fired.UX behavior
Empty state renders when:
DataLoadingState.loaded)total === 0Two copy variants
triggerId: …)Scope detection uses
isDefaultTriggerEventSearchScope()(compares submitted KQL tobuildDefaultTriggerEventSearchQuery()).🎥 Demo
Screen.Recording.2026-05-29.at.23.39.21.mov