I was able to reproduce this by having an agent run that calls pxExtractDataWithArgs. It looks as if it did turn off Rule Caching (SMA > Advanced > Rule Cache Management).
It seems you may have found a bug, but it's possible this is expected for some reason. Hopefully someone more directly connected to the code can explain this behavior and or confirm that this is a bug.
Sorry I missed that you are running BIX from an agent, but not from command line. If you run BIX from command line, there is an enable call in the finally block.
after extract is done. Your current scenario is a different execution path. It appears to be missing enable call after extract is done. Yes, it does look like an oversight to me. Once this is confirmed by SME, you should go head with a SR.
Thank you for your email. Would you please elaborate the effect of cache disabled? It seems that the cache is disabled on a node in which BIX agent run? Trying to think of some options at the moment: What will be an impact on performance when the BIX agent runs on a separate node dedicated to the running of BIX, and the cache is disabled all the time. No users would be routed to the node. Does the disable of rule cache on a bix node have any other impact for bix agent itself or other users or nodes?