SYMPTOM
In Strategy Secure Enterprise 2020 and newer, document caches created via subscription cannot be hit by some users despite there being no difference in security filters or prompt answers. It is seen instead that a second document cache is created when the document is executed and users can correctly hit this cache.
CAUSE
One possible cause for this issue is different flags applied to the caches tied to the permission "Execute Transaction" under Project Access > Common Privileges. In order to confirm this, the Strategy Cache Parser can be used. Directions for this are at:
KB30309: How to use the Cache Parser tool to read cache information from information and lookup files and user inbox messages
It will be seen that the Result Flag for the subscription generated cache will have an extra 0x800000 flag applied to it as shown below because the user account triggering the subscription has this additional privilege:
Subscription Cache Result Flag: Result Flag : 0x848343 User Generated Result Flag: Result Flag : 0x48343