rogermesengeotec
I have seen issues similar to this before. The output will "break" and stop reading the input data for unspecified reasons. I have found that recreating the output often fixes the issue, but you are right. This is not feasible for a day-to-day practice. However, there could be something else at play here.
If you would like, I would encourage you to open a case with Esri Support to see if they can maybe take a closer look for you. If the analyst cannot find anything specific to what causes this breakage, they can at least reach out to additional resources who may know more.
Keep in mind that there are a multitude of different environmental variables that can play a role in Geoevent service performance. External factors like a SSL certificate expiring, server crashes, system updates, etc. can all possibly affect your server throughput. On the internal, GeoEvent Server-side, things like changes to the definition or input/output configurations can also cause a break in performance if you fail to stop the involved components first (i.e. Changing a field name in the definition while the input is running).
Hope this helps!