In V2.4.0 there was the auto_disable stanza line to keep every input enabled (had to set in the input config with every input, not possible from splunkweb, should be one overall setting from the console). Since the update the documentation says
Retry policy on scheduled task failures is changed
Rapid retry policy of scheduled tasks for failing inputs and outputs is disabled. DB Connect 3 does not retry failed tasks until the next interval. Consequently, the auto_disable setting is deprecated; it will not cause configuration validation errors, but it is no longer functional.
We now notice that for example some queries on a database get disabled, whilst others continue to stay enabled. "the next interval" - some jobs are set to run every few minutes, they however stay disabled. When enabling manually, they actually run and stay active.
Not sure if it's a bug or what exactly is the 'next interval'? More important would be the possibility to auto-re-enable or at least have some monitoring query to point out inputs going to disabled.
