This issue is true for all workflow plugins using OSWorkflow 2.8.0 version.

AbstractWorkflow has a local thread cache into which result of passesConditions is stored for each requested workflow actions.

The cache is clear only when doing workflow action for real, in transitionWorkflow function.
If an action X is invalid for a content C1, transitionWorkflow is not executed and the cache is not clear. So the action X is stored as invalid in cache.

Now if the doAction is called with same action X and same thread on a other content C2, the cache will answer that action is invalid, trusting its cache, even if the action X was valid for this content.

This issue can be demonstrated during the execution of the same workflow action on a large number of contents in a same thread