There are 884 scheduled processes just sitting there for pyFTSIncrementalIndexer. Also, there are scheduled processes for pzStandardProcessor and pyProcessNotification and broken processes for pyBatchIndexProcessor (as see in attachment).
Don't know if these are causing an issue with pyFTSIncrementalIndexer or visa versa.
All queue processors are "running", so why aren't they processing these scheduled processes?
***Edited by Moderator Marije to add Capability tags***
If your queue processor does not work, consider the following:
Queue processor rules rely on the DSM service. In Pega Cloud services and client-managed cloud environments, a stream node is automatically configured and ready to use. For on-premises environments, ensure that you define at least one node in a cluster to be a Stream node using the setting: -DNodeType=Stream. For more information, see Stream node configurations for a queue processor rule.
@MarijeSchillern The issue is that we have recently done an upgrade and there is quite a bit of bumpiness. First, the Stream Service keeps going down (still happening pretty much every day), so we re-start it. Second, the Search settings keep having to be re-entered for the Host Node ID and File Directory. Once those 2 things are done, it seems to work correctly.