In the ATG logs you may see warnings about a slot being session scoped not global.
[STDOUT] Invalid attempt to resolve component /atg/registry/Slots/ActivationFlowSlot in scope global. It is defined in scope session
Most of the time you can safely ignore these warnings because these warnings are most likely coming from the ACC.
When browsing slots using the ACC the ACC tries to look up the slot as a global component and complains it’s a session scoped component. In other words it’s an ACC bug that will probably never be fixed since ATG is moving away from the ACC.