Good catch, missed that myself. Took a closer look with dynamic targeting and found the below relevance works for the count for both dynamic and static targeting. It’s not elegant but seems to work pretty well for just the open action count. Still looking into couple other options into getting more info (pending actions on hold, etc.) than just the count into the console but with the information in multiple places gets a bit complicated. Let me know if I missed anything.
(number of files whose(name of it as string as lowercase ends with “qid” AND line of it contains “pending”) of folder “__Local” of folder “actionsite” of data folder of client) + (number of files whose(name of it as string as lowercase contains “action”) of folder “mailboxsite” of data folder of client)
Edit – Just found a flaw in this myself with multiple action groups not being counted and static targets from second half of relevance being double counted from mailbox and local folder. Just happened to be the same number of multiple action groups and static actions in my test cases. Leaving the original relevance up since there is a few options that could be useful to some users.