IntegrityError: null value in "notifications" column of core_job when triggering bulk-scan / Ping Selected

[exzaunno]

ACTUAL BEHAVIOR
_HTTP 500 Server Error. The plugin attempts to create a job in the core_job table but does not pass a value for the notifications column, which was introduced as NOT NULL in NetBox 4.5.
<class 'django.db.utils.IntegrityError'>

null value in column "notifications" of relation "core_job" violates not-null constraint
DETAIL: Failing row contains (93, null, Prefix Scan, 2026-05-29 09:22:47.754683+00,
null, null, null, null, pending, null, 0ccc4db6-4914-4a32-8ae5-7d53d3ca08b2,
null, 4, , {}, default, null).

Request: GET /plugins/netbox-ping/bulk-scan/?pk=2_

ROOT CAUSE ANALYSIS
NetBox 4.5 introduced the notifications column on the core_job table with a NOT NULL constraint. The plugin creates background jobs without setting this field — likely missing notifications=[] (or an equivalent empty value) in the job creation call.

Is there a upcoming fix planned or maybe it's possible to set a default value for the affected table entry?

Thanks

[pheus]

Hi,

NetBox v4.5 is a breaking-change-allowed release under the tick-tock release model: #19899

This means plugin maintainers may need to update their plugins to account for changes introduced in NetBox v4.5.

Based on the error, this looks like an issue in the plugin’s job creation code. The plugin likely needs to provide a value for the new notifications field when creating the background job.

I’d recommend opening an issue or discussion in the plugin’s repository and following their contribution guidelines.

Hope that helps a little!