Recurring job execution time is inaccurate

Nobody has claimed this yet.


My config:

var options = new SqlServerStorageOptions
{
SlidingInvisibilityTimeout = TimeSpan.FromMinutes(5),
QueuePollInterval = TimeSpan.Zero
};

builder.Services.AddHangfire(configuration => configuration.SetDataCompatibilityLevel(CompatibilityLevel.Version_180)
.UseSimpleAssemblyNameTypeSerializer().UseRecommendedSerializerSettings()
.UseSqlServerStorage(schedulerSetting.ConnectionString, options)
.UseFilter(new AutomaticRetryAttribute { Attempts = 0 })
.UseFilter(new DisableConcurrentExecutionAttribute (schedulerSetting.ConcurrentExecutionTimeoutSeconds))
.UseSerilogLogProvider()
);

Cron: "59 * * * * *"

hangfire version:

The program's local time is 4 seconds faster than the database; Each execution of the schedule is slower than the last time;Please help please.

Start by reproducing the supplied configuration and six-field Cron schedule while comparing application and database clocks. Determine why successive recurring executions drift in timing, and consider the issue done when executions occur at the intended schedule despite the reported four-second clock difference.

Written by the indexing model from the issue text.