Hi Tucker,
I'll add to Jake's comment with a little more detail into what could be occurring with GeoEvent. The behavior you describe sounds like a error behavior in GeoEvent related to the RabbitMQ platform service. This service facilitates the movement of messages from the inputs, through the services and to the outputs within GeoEvent. It's normally the first thing that is assumed to be wrong when both the GeoEvent Services and Output connectors are not increasing in count. We discovered this error starting at the 10.3.x release, and it has been addressed in the 10.4.x release. The only exception is that we still observe it within some user environments or within AWS environments using the Esri AMI. The latter is due to a internal software conflict within AWS that is very hard to reproduce. Can you tell me what version of GeoEvent you are using, as well as if you see any large error messages in the GeoEvent logs? Normally the GeoEvent logs will contain references to the RabbitMQ service if this is truly the cause.
-Chris