Rapid or multiple firing Jobs

Some Informers on 5.10+ (including 2025.1+) have seen Jobs fire more than once within a few minutes, or fire repeatedly in rapid succession. The fix for both is the same: give Informer more database connections and a longer Job heartbeat. Both changes go in config.json (in the Informer root install) for Windows and Docker alike. Save the file and restart Informer to apply them.

• Database connection pool. The Job worker threads need free PostgreSQL connections to report status. The default is 5; start at 20 for an Informer with this issue:

"db": {
  "pool": {
    "max": 20
  }
}

• Job heartbeat. A longer heartbeat gives Informer more time to communicate Job status internally, which prevents a Job from being retriggered. The default is 1 second (1000); start at 30 seconds:

"schedule": {
  "jobHeartbeatMillis": 30000
}

An Informer that hit this issue probably has locked Jobs afterward. Clear them with Fully reset the Job queue.