Re-execute after throwing exception incorrect docs

[tompazourek]

Hi, I'm reading the docs (https://www.quartz-scheduler.net/documentation/best-practices.html#throwing-exceptions) and it contains this:

If a job throws an exception, Quartz will typically immediately re-execute it, meaning the job can and likely will throw the same exception again.

Is this actually true? I've been both testing this and reading the code, and it seems that when an exception occurs, the JobRunShell converts it to JobExecutionException with refireImmediately: false:

quartznet/src/Quartz/Core/JobRunShell.cs

Lines 222 to 230 in fe5420a

	catch (Exception e)
	{
	endTime = qs.resources.TimeProvider.GetUtcNow();
	logger.LogError(e, "Job {JobDetailKey} threw an unhandled Exception: ", jobDetail.Key);
	SchedulerException se = new SchedulerException("Job threw an unhandled exception.", e);
	string msg = $"Job {jec.JobDetail.Key} threw an exception.";
	await qs.NotifySchedulerListenersError(msg, se, cancellationToken).ConfigureAwait(false);
	jobExEx = new JobExecutionException(se, false);
	}

The exception without refire will get converted to scheduler instruction (refireImmediately: false will convert to SchedulerInstruction.NoInstruction):

quartznet/src/Quartz/Impl/Triggers/AbstractTrigger.cs

Lines 435 to 457 in fe5420a

	public virtual SchedulerInstruction ExecutionComplete(IJobExecutionContext context, JobExecutionException? result)
	{
	if (result != null && result.RefireImmediately)
	{
	return SchedulerInstruction.ReExecuteJob;
	}
	if (result != null && result.UnscheduleFiringTrigger)
	{
	return SchedulerInstruction.SetTriggerComplete;
	}
	if (result != null && result.UnscheduleAllTriggers)
	{
	return SchedulerInstruction.SetAllJobTriggersComplete;
	}
	if (!GetMayFireAgain())
	{
	return SchedulerInstruction.DeleteTrigger;
	}
	return SchedulerInstruction.NoInstruction;

This then means that the fired trigger will be marked as completed and no re-execution will happen. This is the opposite to what the documentation says.

Is this indended behavior? If yes, I think the documentation should be fixed. What do you think?

Thanks.