[BUG] Filtering executions by status in the UI doesn't always work

[katrogan]

Describe the bug
Filtering workflow executions by status sometimes works. An unfiltered view might show a mix of failed and successful executions and filtering by success does indeed show the successful executions but filtering by failed shows nothing.

Expected behavior
Filters should filter specific executions by phase

Flyte component

• Overall
• Flyte Setup and Installation scripts
• Flyte Documentation
• Flyte communication (slack/email etc)
• FlytePropeller
• FlyteIDL (Flyte specification language)
• Flytekit (Python SDK)
• FlyteAdmin (Control Plane service)
• FlytePlugins
• DataCatalog
• FlyteStdlib (common libraries)
• FlyteConsole (UI)
• Other

To Reproduce
Steps to reproduce the behavior:

1. ...
2. ...

Screenshots
If applicable, add screenshots to help explain your problem.

Environment
Flyte component

• Sandbox (local or on one machine)
• Cloud hosted
  • AWS
  • GCP
  • Azure
• Baremetal
• Other

Additional context
Add any other context about the problem here.

[katrogan]

cc @schottra

[schottra]

This seems to be a confusing UX pattern. The "today" and "yesterday" filters are ambiguous about what time range is being used. All times in the UI are based on UTC and the logic of the "today" filter is to take the current UTC time, round down to midnight, and search for any executions that start after that time. For users in PST/PDT, this would have the effect of searching for executions in the future if used after 4 or 5pm.
Some options:

• Update the today/yesterday filters to be based on local time
• Update the UI to display the actual value being filtered on, and notify the user that filters are UTC-based.
• Update the "today" filter to be "last 24 hours", and do a similar thing with the "yesterday" filter (last 48 hours or 24-48 hours ago).