Scheduled Job has Started Sooner than Defined Time

[ZenMaxe]

I’ve observed that a job scheduled with BackgroundJob.Schedule has started before its defined UTC execution time.

In my case:

Scheduled time: 2025-08-13T09:51:48.509664Z

Actual execution start (from logs): 2025-08-13T09:51:48.375Z

Difference: ~134 milliseconds early

the compare code:
if (project.ExpirationDate >= DateTime.UtcNow)

schedule code:

   _backgroundJobClient.Schedule<IProjectExpirationService>(x => x.CheckAndExpireProjectAsync(
            notification.DomainEvent.ProjectId, CancellationToken.None), notification.DomainEvent.ExpirationDate);

ExpirationDate is UTC DateTime

[xavierjefferson]

This will depend on the storage provider you're using, and the precision capabilities of its datetime/timestamp data types. You can't force more precision than the storage provider can supply.

[ZenMaxe]

This will depend on the storage provider you're using, and the precision capabilities of its datetime/timestamp data types. You can't force more precision than the storage provider can supply.

im using Postgresql, there is a problem with postgresql?

[markalanevans]

We just saw the same thing and it's stored in Redis. @odinserj this was for a recurring job. It's been working fine for years. but on 8/25 two jobs triggered on 8/26 and should have triggered on 8/27.