The cron expression on your portal UI requires 5 parameters but only triggers on 6

Question

The cron expression on your portal UI requires 5 parameters but only triggers on 6

Bret Wagner 15

I've been creating webjobs for years. Your UI used to require a 6 parameter cron expression but now it throws a validation error when you use 6. It only allows a 5 parameter expression. It appears that the {second} parameter is not accepted. However, the job never runs when you use the 5 parameter expression. You have to go into the settings.job file to alter the expression in order for the job to actually run.

Aditya N 3,890 Reputation points Microsoft External Staff Moderator

2026-03-20T13:37:30.02+00:00

Hello @Bret Wagner

Thank you for reaching out Microsoft Q&A. We're looking into your query, we'll get back to you shortly.
Golla Venkata Pavani 7,535 Reputation points Microsoft External Staff Moderator

2026-03-20T14:11:03.1266667+00:00
Hello @Bret Wagner

Thank you for reaching us regarding the issue.

This behavior is due to a known mismatch between the Azure Portal UI validation and the Azure WebJobs runtime, not a change in how WebJobs scheduling works.

Azure WebJobs use NCRONTAB, which requires six fields (seconds, minutes, hours, day, month, day‑of‑week), and this format is explicitly documented by Microsoft.
The good news is there’s a supported workaround that bypasses the portal validation by defining the schedule in a settings.job file.

In your WebJob’s root folder (inside the ZIP), create a file called settings.job with the following content (adjust the schedule as needed):

{ "schedule": "0 0 9 * * *" }

Then:

Zip the WebJob package and upload it via the portal under Triggered > Upload your zip (you can choose Manual trigger during upload).

Go to Configuration > General settings and set Always On = Yes (required for scheduled WebJobs on Basic/Standard/Premium tiers).

You can verify execution from the WebJobs blade or via Kudu logs.

This behavior and workaround are aligned with Microsoft documentation and guidance for scheduled WebJobs using NCRONTAB expressions.

Reference :
https://learn.microsoft.com/en-us/azure/app-service/webjobs-create?tabs=windowscode#ncrontab-expressions
https://learn.microsoft.com/en-us/azure/app-service/tutorial-webjobs?tabs=windows&pivots=dotnet

Kindly let us know if the above helps or you need further assistance on this issue.

Please "accept" if the information helped you. This will help us and others in the community as well.
Golla Venkata Pavani 7,535 Reputation points Microsoft External Staff Moderator

2026-03-23T09:10:11.4166667+00:00

Hello @Bret Wagner

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?
Bret Wagner 15 Reputation points

2026-03-31T12:53:51.7+00:00

Hello,

No. It has not been resolved. The cron expression in your UI only allows 5 parameters but will only run with 6. You have to go to the settings.job file to modify the cron expression.
Bret Wagner 15 Reputation points

2026-03-31T12:55:43.62+00:00

This is a "new" issue as I've been able to add the 6 parameter cron expression in the portal UI for years. Are there plans to fix this "known" issue?

This behavior is due to a known mismatch between the Azure Portal UI validation and the Azure WebJobs runtime, not a change in how WebJobs scheduling works.
Shree Hima Bindu Maganti 7,590 Reputation points Microsoft External Staff Moderator

2026-03-31T14:39:55.3833333+00:00

Hello @Bret Wagner
Apology for your inconvenience
The behavior you are experiencing is due to a known mismatch between the Azure Portal UI validation and the Azure WebJobs runtime. Azure WebJobs scheduling is based on the NCRONTAB format, which requires a 6-field cron expression including the seconds field ({second} {minute} {hour} {day} {month} {day-of-week}). However, the Azure Portal UI currently validates only a 5-field expression and incorrectly rejects valid 6-field schedules. As a result, schedules entered through the portal may pass validation but will not trigger as expected at runtime. The WebJob executes correctly only when a proper 6-field NCRONTAB expression is defined directly in the settings.job file. This is a known limitation, and the recommended workaround is to configure or update the schedule in the settings.job file using the 6-field format.
https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-timer?tabs=python-v2%2Cisolated-process%2Cnodejs-v4&pivots=programming-language-csharp
https://learn.microsoft.com/en-us/azure/app-service/webjobs-create?tabs=windowscode
Kindly let us know if the above helps or you need further assistance on this issue.
WebMatik 0 Reputation points

2026-04-07T09:51:53.7733333+00:00

Hello @Golla Venkata Pavani i'm adding to Bret's request because also for me there is this problem and it's very boring. Tried also adding settings.job file with 6 fields cron but the interface show the result translated in 5 fields so it's unclear
Shree Hima Bindu Maganti 7,590 Reputation points Microsoft External Staff Moderator

2026-04-08T16:35:29.34+00:00
Hello @Bret Wagner
Thank you for the update. What you are observing is expected behavior due to how the Azure Portal displays the schedule. Even if you define a valid 6-field NCRONTAB expression in the settings.job file, the Portal UI may still render or “translate” it into a 5-field format, which can be misleading. This display does not reflect how the WebJob is actually executed. The underlying WebJobs runtime continues to use the 6-field NCRONTAB expression defined in settings.job, including the seconds field, regardless of how it appears in the UI.

To confirm the actual behavior, it is recommended to rely on execution evidence rather than the portal display:

Check WebJob run history and timestamps

Review logs via Kudu (https://<appname>.scm.azurewebsites.net)

Validate trigger intervals against the expected 6-field schedule

As per Microsoft documentation, WebJobs scheduling is based on NCRONTAB (6 fields), and the settings.job file is the authoritative configuration source:

https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-timer?tabs=python-v2%2Cisolated-process%2Cnodejs-v4&pivots=programming-language-csharp
https://learn.microsoft.com/en-us/azure/app-service/webjobs-create?tabs=windowscode
Kindly let us know if the above helps or you need further assistance on this issue.

Your answer

Aditya N 3,890 Reputation points Microsoft External Staff Moderator

2026-03-20T13:37:30.02+00:00

Hello @Bret Wagner

Thank you for reaching out Microsoft Q&A. We're looking into your query, we'll get back to you shortly.
Golla Venkata Pavani 7,535 Reputation points Microsoft External Staff Moderator

2026-03-20T14:11:03.1266667+00:00

Hello @Bret Wagner

Thank you for reaching us regarding the issue.

This behavior is due to a known mismatch between the Azure Portal UI validation and the Azure WebJobs runtime, not a change in how WebJobs scheduling works.

Azure WebJobs use NCRONTAB, which requires six fields (seconds, minutes, hours, day, month, day‑of‑week), and this format is explicitly documented by Microsoft.
The good news is there’s a supported workaround that bypasses the portal validation by defining the schedule in a settings.job file.

In your WebJob’s root folder (inside the ZIP), create a file called settings.job with the following content (adjust the schedule as needed):

{ "schedule": "0 0 9 * * *" }

Then:

Zip the WebJob package and upload it via the portal under Triggered > Upload your zip (you can choose Manual trigger during upload).

Go to Configuration > General settings and set Always On = Yes (required for scheduled WebJobs on Basic/Standard/Premium tiers).

You can verify execution from the WebJobs blade or via Kudu logs.

This behavior and workaround are aligned with Microsoft documentation and guidance for scheduled WebJobs using NCRONTAB expressions.

Reference :
https://learn.microsoft.com/en-us/azure/app-service/webjobs-create?tabs=windowscode#ncrontab-expressions
https://learn.microsoft.com/en-us/azure/app-service/tutorial-webjobs?tabs=windows&pivots=dotnet

Kindly let us know if the above helps or you need further assistance on this issue.

Please "accept" if the information helped you. This will help us and others in the community as well.
Golla Venkata Pavani 7,535 Reputation points Microsoft External Staff Moderator

2026-03-23T09:10:11.4166667+00:00

Hello @Bret Wagner

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?
Bret Wagner 15 Reputation points

2026-03-31T12:53:51.7+00:00

Hello,

No. It has not been resolved. The cron expression in your UI only allows 5 parameters but will only run with 6. You have to go to the settings.job file to modify the cron expression.
Bret Wagner 15 Reputation points

2026-03-31T12:55:43.62+00:00

This is a "new" issue as I've been able to add the 6 parameter cron expression in the portal UI for years. Are there plans to fix this "known" issue?

This behavior is due to a known mismatch between the Azure Portal UI validation and the Azure WebJobs runtime, not a change in how WebJobs scheduling works.
Shree Hima Bindu Maganti 7,590 Reputation points Microsoft External Staff Moderator

2026-03-31T14:39:55.3833333+00:00

Hello @Bret Wagner
Apology for your inconvenience
The behavior you are experiencing is due to a known mismatch between the Azure Portal UI validation and the Azure WebJobs runtime. Azure WebJobs scheduling is based on the NCRONTAB format, which requires a 6-field cron expression including the seconds field ({second} {minute} {hour} {day} {month} {day-of-week}). However, the Azure Portal UI currently validates only a 5-field expression and incorrectly rejects valid 6-field schedules. As a result, schedules entered through the portal may pass validation but will not trigger as expected at runtime. The WebJob executes correctly only when a proper 6-field NCRONTAB expression is defined directly in the settings.job file. This is a known limitation, and the recommended workaround is to configure or update the schedule in the settings.job file using the 6-field format.
https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-timer?tabs=python-v2%2Cisolated-process%2Cnodejs-v4&pivots=programming-language-csharp
https://learn.microsoft.com/en-us/azure/app-service/webjobs-create?tabs=windowscode
Kindly let us know if the above helps or you need further assistance on this issue.
WebMatik 0 Reputation points

2026-04-07T09:51:53.7733333+00:00

Hello @Golla Venkata Pavani i'm adding to Bret's request because also for me there is this problem and it's very boring. Tried also adding settings.job file with 6 fields cron but the interface show the result translated in 5 fields so it's unclear
Shree Hima Bindu Maganti 7,590 Reputation points Microsoft External Staff Moderator

2026-04-08T16:35:29.34+00:00

Hello @Bret Wagner
Thank you for the update. What you are observing is expected behavior due to how the Azure Portal displays the schedule. Even if you define a valid 6-field NCRONTAB expression in the settings.job file, the Portal UI may still render or “translate” it into a 5-field format, which can be misleading. This display does not reflect how the WebJob is actually executed. The underlying WebJobs runtime continues to use the 6-field NCRONTAB expression defined in settings.job, including the seconds field, regardless of how it appears in the UI.

To confirm the actual behavior, it is recommended to rely on execution evidence rather than the portal display:

Check WebJob run history and timestamps

Review logs via Kudu (https://<appname>.scm.azurewebsites.net)

Validate trigger intervals against the expected 6-field schedule

As per Microsoft documentation, WebJobs scheduling is based on NCRONTAB (6 fields), and the settings.job file is the authoritative configuration source:

https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-timer?tabs=python-v2%2Cisolated-process%2Cnodejs-v4&pivots=programming-language-csharp
https://learn.microsoft.com/en-us/azure/app-service/webjobs-create?tabs=windowscode
Kindly let us know if the above helps or you need further assistance on this issue.