Renovate enqueues jobs for repos even though MEND_RNV_ENQUEUE_JOBS_ON_STARTUP is disabled

[paymand]

I'm using the latest helm chart and have set mendRnvEnqueueJobsOnStartup: "disabled" in my values.yml file hoping to not get any jobs enqueued on startup.

Looking at the logs, I see:
Sync and enqueue job startup mode with the following content:

{
	"id": "AwAAAZqXm_cZ1DvQpAAAABhBWnFYbV9sdEFBQ1FtYTgxcHNCUlNBQUgAAABdMTE5YTk3OWYtMDM3Yi00ZWQ5LWI4YjQtYThiMzQ5N2I0NTgwLXN5bnRoZXRpYy10aW1lLTE3NjM0NzgwMDAwMDAwMDAwMDBjLTE3NjM0ODAzNzIwOTEwMDAwMDFvAAAllA",
	"content": {
		"timestamp": "2025-11-18T15:36:12.313Z",
		"tags": [
			...
		],
		"host": "renovate-mend-renovate-ce-5cdc7bb556-6tz4k",
		"service": "renovate-ce",
		"message": "Sync and enqueue job startup mode",
		"attributes": {
			"syncOnStartup": true,
			"hostname": "renovate-mend-renovate-ce-5cdc7bb556-6tz4k",
			"level": 30,
			"v": 0,
			"name": "mend-renovate",
			"syncMode": "batch",
			"pid": 8,
			"logContext": "XvAptyNNvPXQ6ZomyQLJe",
			"time": "2025-11-18T15:36:12.313Z",
			"enqueueJobsOnStartup": "disabled",
			"status": "Info"
		}
	}
}

so we have set "enqueueJobsOnStartup": "disabled",, but later on we still end up enqueuing jobs for discovered repos!

{
	"id": "AwAAAZqXm_3YzdF1MAAAABhBWnFYbkFGVkFBQkVXYmJrQU5JMW5BQUEAAABdMTE5YTk3OWYtMDM3Yi00ZWQ5LWI4YjQtYThiMzQ5N2I0NTgwLXN5bnRoZXRpYy10aW1lLTE3NjM0NzgwMDAwMDAwMDAwMDBjLTE3NjM0ODAzNzIwOTEwMDAwMDFvAAAhUg",
	"content": {
		"timestamp": "2025-11-18T15:36:14.040Z",
		"tags": [
			...
		],
		"host": "renovate-mend-renovate-ce-5cdc7bb556-6tz4k",
		"service": "renovate-ce",
		"message": "Enqueueing jobs for newly discovered repositories",
		"attributes": {
			"hostname": "renovate-mend-renovate-ce-5cdc7bb556-6tz4k",
			"level": 20,
			"v": 0,
			"name": "mend-renovate",
			"pid": 8,
			"logContext": "XvAptyNNvPXQ6ZomyQLJe",
			"time": "2025-11-18T15:36:14.040Z",
			"status": "Debug"
		}
	}
}

@nabeelsaabna Does this make any sense, or am I missing something?

[nabeelsaabna]

MEND_RNV_ENQUEUE_JOBS_ON_STARTUP: The job enqueue behavior on start (or restart). Defaults to discovered. (Note that the behavior can be different if the database is persisted or not)

enabled: enqueue a job for all available repositories
discovered: enqueue a job only for newly discovered repositories
disabled: No jobs are enqueued

According to the docs and your description there seems to be a bug! Will test this and keep you posted.

In case you have a persisted database then you can try the startup-and-sync-behavior recommendation of setting MEND_RNV_SYNC_ON_STARTUP = false and aslo MEND_RNV_ENQUEUE_JOBS_ON_STARTUP = disabled as a temporary workaround

[paymand]

We don't persist the DB in our setup, but still hoping to disable enqueuing jobs on startup. Not a blocker for us, but will be great to get it fixed. Thank you 🙏

[nabeelsaabna]

when using below settings it works expected

MEND_RNV_ENQUEUE_JOBS_ON_STARTUP = disabled
MEND_RNV_SYNC_ON_STARTUP = true
MEND_RNV_SYNC_MODE = bulk

But switch the sync-mode batch causes an issue when combined with

MEND_RNV_ENQUEUE_JOBS_ON_STARTUP = disabled
MEND_RNV_SYNC_ON_STARTUP = true
MEND_RNV_SYNC_MODE = batch

so instead of the above workaround you can use the default sync-mode bulk as it will successfully sync 1k+ repos without any problems (therefor no real reason for CE to use sync-mode batch )

[paymand]

Hi @nabeelsaabna the workaround with bulk mode did the trick. Fee free to keep this issue if you plan to fix it or close it if you don't. Thanks 🙏