# Why does a flag exist but not show in my view?

**URL:** <https://community.dockflow.com/t/why-does-a-flag-exist-but-not-show-in-my-view/160>\
**Category:** How-to Q&A\
**Tags:** area-automations, flags-and-alerts\
**Created:** [November 6, 2026, 3:17pm UTC](https://community.dockflow.com/t/why-does-a-flag-exist-but-not-show-in-my-view/160 "2026-11-06T15:17:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dockflow](https://community.dockflow.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@dockflow](https://community.dockflow.com/u/dockflow)\
**Post date:** [November 6, 2026, 3:17pm UTC](https://community.dockflow.com/t/why-does-a-flag-exist-but-not-show-in-my-view/160/1 "2026-11-06T15:17:57Z")

</div>

Flags can be set at **container level** or at **tradeflow level** , and a view groups at one level  
or the other. If an automation sets a flag on the container while the view groups by tradeflow, the  
flag will not surface there, even though it exists.

**What to check:** the level the automation sets the flag at, against the level the view groups by.  
They need to match for the flag to be visible.

This is worth knowing before assuming a flag was never created. It is normally visible in the  
overview but absent from the tabs, or the reverse.

**Example**  
An automation sets a flag at container level, but the view groups by tradeflow. The flag exists, yet it does not appear in that view. The fix is to check the level the automation sets the flag at against the level the view groups by; they must match for the flag to be visible. It may also appear in the overview but be absent from the tabs.