@alexus do you happen to know if the instances share the same reporting index? We've found that if all kibana instances use different indexes there can be issues with how reporting works:
Multiple kibana.index settings across Kibana instances : if each instance a unique kibana.index setting but has the same xpack.reporting.index setting, it's possible that workers can claim a job that they aren't able to fulfill. The job will contain references to saved objects that the instance doesn't have in its own kibana.index .
-
Solution : With different
kibana.indexsettings across Kibana instances connected to the same Elasticsearch cluster, you must also configure a differentxpack.reporting.indexsetting per each uniquekibana.index
This assumes you have a few instances running (which I'm not sure if you do). It'd also be good to see your other env variables just to know more about the environment itself.