Job running with old instance of code

[hello2pankaj]

I am using Quartz.Extensions.Hostin 3.8.1 scheduling package in .netcore6 web api application. App deployment environment is azure appservice (running on 2 instances). I have below quartz config for 4 jobs.

public static void ConfigureQuartzJobs(this WebApplicationBuilder builder)
{
	var services = builder.Services;
	services.AddQuartzHostedService(opt => opt.WaitForJobsToComplete = true);
	services.AddQuartz(q =>
	{
		q.SchedulerId = "SomeId";
		q.SchedulerName = "SomeName";
		q.UsePersistentStore(s =>
				{
				  s.UseProperties = true;
				  s.UseClustering();
				  s.UseSqlServer(connectionString);
				  s.UseNewtonsoftJsonSerializer();
				});
				q.AddJob<job1>(j => j.StoreDurably().WithIdentity(jobkey1))
				 .AddTrigger(trigger => trigger
						   .ForJob(jobkey1)
						   .WithIdentity("tr1")
						   .WithSimpleSchedule(schedule => schedule.WithIntervalInMinutes(5).RepeatForever()));
						   

				q.AddJob<job2>(j => j.StoreDurably().WithIdentity(jobkey2))
				 .AddTrigger(trigger => trigger
						   .ForJob(jobkey3)
						   .WithIdentity("tr2")
						   .WithSimpleSchedule(schedule => schedule.WithIntervalInMinutes(5).RepeatForever()));
						   

				q.AddJob<job3>(j => j.StoreDurably().WithIdentity(jobkey3))
				 .AddTrigger(trigger => trigger
						   .ForJob(jobkey3)
						   .WithIdentity("tr3")
						   .WithSimpleSchedule(schedule => schedule.WithIntervalInMinutes(5).RepeatForever()));
						   

				q.AddJob<job4>(j => j.StoreDurably().WithIdentity(jobkey4))
				 .AddTrigger(trigger => trigger
						   .ForJob(jobkey4)
						   .WithIdentity("tr4")
						   .WithSimpleSchedule(schedule => schedule.WithIntervalInMinutes(60).RepeatForever()));
	});
}

Let say job1 calls instance of LogicClass which has method "Process(bool CalledByJob)". It is called by Job1 class something like below.

[DisallowConcurrentExecution]
public class Job1 : IJob
{
	public async Task Execute(IJobExecutionContext context)
	{
		try
		{
		   logicClass.Process(True);
		}
		catch (Exception ex)
		{
			await Console.Out.WriteLineAsync($"{context.FireTimeUtc}, {ex}. FireInstanceId={context.FireInstanceId}");
		}
	}
}

LogicClass's process method has code to log saying "Processing start. CalledByJob={calledbyJob}"

So when the job starts, i can see the log happening which is expected.

However , when i was done with testing, i removed the part "CalledByJob={calledbyJob}" from the log. The log now only said "Processing start".

The issue i am seeing is that after deployment of the code (i.e without CalledByJob log), some job run is showing it (i.e. "calledByJob=true") in the log and some not. I tried restarting the azure app service and Purging the azure front door cache. no luck though.

Can anyone please guide me why this is happening and what's the solution.

[hello2pankaj]

Hi @lahma , what should i do to resolve this? See below screen grab. I deployed the code to include the build number (BuildNumber=1.2405.23.2) in the log. then again deployed the code so that new build number (BuildNumber=1.2405.23.3) start appearing in the log. However, it is seen that the quartz.net is running code from both the builds. See below. Green one is latest build and yellow is the earlier build. I tried a lot since my original post above but this is always the case. Restarting server also doesn't help. Can you please guide.

Additional info - I am not using static variables. Job runs for not more than 1 second. Logs are in by time desc so i should see build 1.2405.23.3 as the top entry but seeing 1.2405.23.2.

[hello2pankaj]

The prod slot need to run continuously as the job does important stuff which are time sensitive.

[lahma]

Yes, run in production, not in staging.

[hello2pankaj]

Did not understood. Its quartz.net which is deciding to run from stage slot or prod slot.

Also here, if i am not clear, when i say stage slot i am not talking about staging environment. All my environment (test, stage, prod) has 2 slots (stage and prod). So i am talking about slots and not environment. hope i am making sense.

[lahma]

Quartz doesn't decide to start/run. You are starting it via code.

[hello2pankaj]

Understood . but how to resolve this scenario.