Hi @Deep
I heard back from the engineering team and they said there isn’t a hardcoded maximum.
kudu/DeploymentSettingsExtension.cs at master · projectkudu/kudu (github.com)
public static int GetWebJobsHistorySize(this IDeploymentSettingsManager settings)
{
string value = settings.GetValue(SettingsKeys.WebJobsHistorySize);
int maxJobRunsHistoryCount;
if (Int32.TryParse(value, out maxJobRunsHistoryCount) && maxJobRunsHistoryCount > 0)
{
return maxJobRunsHistoryCount;
}
return DefaultMaxJobRunsHistoryCount;
}
There would be a balance between setting higher numbers for these values and not consuming too much disk space.
An alternative is to consider enabling Application Insights logging: Tutorial for event-driven background processing with the WebJobs SDK - Azure App Service | Microsoft Learn
Hope that helps.
Best,
Grace