Executions Hidden for System Flows Due to Incorrect Default Scope Filter

[lxRavenxl]

Describe the issue

According to the System-flow documentation, executions of the flows created in the system namespace should be visible only within that namespace by default using filter scope=SYSTEM

However, the Executions view in the system namespace incorrectly applies scope=USER as the default filter. This causes executions of system flows to be hidden, even though they exist and are running successfully.

This behavior is inconsistent with the documented and expected behavior of system flows.

Use Case

• Create a flow in the system namespace.
• Execute the flow.
• Navigate to:
  Namespaces → System → Executions

Expected Behavior

• The default filter applied in the system namespace is scope=SYSTEM.
• The most recent execution of the system flow is visible immediately in the executions list.

Observed Behavior

• The default filter applied is scope=USER.
• No execution results are shown, even though the flow executed successfully.
• To see the execution results, the user must:
  • Remove the default scope=USER filter, or
  • Change the filter to scope=SYSTEM.

Additional Information

If you set the default scope=SYSTEM, it becomes defaults for all other namespaces. In other words it is a global change. All namespace execution filter will default to scope=SYSTEM which makes this filter useless.

Environment

• Kestra Version: 1.1.11

[omkarChend1kar]

I would like to look into this. please assign this to me.