Azure Function error when defining a timer

Question

Azure Function error when defining a timer

Guillaume THIERY 0

Hello,

I have deployed a Powershell Function App on Azure. The script works and can be trigerred with :

*/59 * * * * *

From 0 to 59 seconds, it works but I want to run this script every 5 minutes.

When I configure the minutes, the function does not work anymore and I get this error :

2025-05-22T15:04:32Z [Error] Executed 'Functions.ps-test' (Failed, Id=989e2385-f915-4f15-bda3-527c03ec353e, Duration=2ms)

I tried different configurations and it always results in the same error.

*/5 * * * * 0 */5 * * * *

My format seems good but the function fails. What is wrong ? I need to run this script every 5 or 10 minutes, how can I do it ?

Bathini Harshitha 85 Points de réputation Personnel externe de Microsoft Corporation Modérateur

2025-05-27T09:10:31.72+00:00

Bonjour Guillaume THIERY

Pourriez-vous s’il vous plaît partager le code sur lequel vous travaillez ?

Je traduis le commentaire de l’anglais vers le français, alors veuillez me pardonner si j’ai des problèmes de grammaire.

Guillaume THIERY 0

Bonjour @Bathini Harshitha

Je ne peux malheureusement pas partager le code en intégralité car il contient des données sensibles....


# Input bindings are passed in via param block.
param($Timer)

# Get the current universal time in the default string format.
$currentUTCtime = (Get-Date).ToUniversalTime()

# The 'IsPastDue' property is 'true' when the current function invocation is later than scheduled.
if ($Timer.IsPastDue) {
    Write-Host "PowerShell timer is running late!"
}

# Write an information log with the current time.
Write-Host "PowerShell timer trigger function ran! TIME: $currentUTCtime"

$server   = $env:DB_SERVER
$database = $env:DB_NAME
$username = $env:DB_USER
$password = $env:DB_PASS

# Chaîne de connexion
$connectionString = "Driver={ODBC Driver 17 for SQL Server};Server=$server;Database=$database;Uid=$username;Pwd=$password;"

$connection = New-Object System.Data.Odbc.OdbcConnection
$connection.ConnectionString = $connectionString
$connection.Open()

### DEROULEMENT DES OPERATIONS ET ECRITURE EN BDD ###
####
####
####
####

$connection.Close()

Le code a été testé et fonctionne. Comme expliqué, si le trigger est configuré sur */59 * * * * * il n'y a aucun problème et le script est bien exécuté.
Sans apporter de modification au script et ajustant uniquement le trigger, l'erreur partagée ci-dessus est déclenchée.

D'ailleurs, est-ce que ce bloc de code par défaut est nécessaire ou peut être supprimé ?

# Input bindings are passed in via param block.
param($Timer)

# Get the current universal time in the default string format.
$currentUTCtime = (Get-Date).ToUniversalTime()

# The 'IsPastDue' property is 'true' when the current function invocation is later than scheduled.
if ($Timer.IsPastDue) {
    Write-Host "PowerShell timer is running late!"
}

# Write an information log with the current time.
Write-Host "PowerShell timer trigger function ran! TIME: $currentUTCtime"

2 réponses

Votre réponse

Bathini Harshitha 85 Points de réputation Personnel externe de Microsoft Corporation Modérateur

2025-05-27T09:10:31.72+00:00

Bonjour Guillaume THIERY

Pourriez-vous s’il vous plaît partager le code sur lequel vous travaillez ?

Je traduis le commentaire de l’anglais vers le français, alors veuillez me pardonner si j’ai des problèmes de grammaire.
Guillaume THIERY 0 Points de réputation

2025-05-27T12:53:18.3333333+00:00

Bonjour @Bathini Harshitha

Je ne peux malheureusement pas partager le code en intégralité car il contient des données sensibles....

# Input bindings are passed in via param block. param($Timer) # Get the current universal time in the default string format. $currentUTCtime = (Get-Date).ToUniversalTime() # The 'IsPastDue' property is 'true' when the current function invocation is later than scheduled. if ($Timer.IsPastDue) { Write-Host "PowerShell timer is running late!" } # Write an information log with the current time. Write-Host "PowerShell timer trigger function ran! TIME: $currentUTCtime" $server = $env:DB_SERVER $database = $env:DB_NAME $username = $env:DB_USER $password = $env:DB_PASS # Chaîne de connexion $connectionString = "Driver={ODBC Driver 17 for SQL Server};Server=$server;Database=$database;Uid=$username;Pwd=$password;" $connection = New-Object System.Data.Odbc.OdbcConnection $connection.ConnectionString = $connectionString $connection.Open() ### DEROULEMENT DES OPERATIONS ET ECRITURE EN BDD ### #### #### #### #### $connection.Close()

Le code a été testé et fonctionne. Comme expliqué, si le trigger est configuré sur */59 * * * * * il n'y a aucun problème et le script est bien exécuté.
Sans apporter de modification au script et ajustant uniquement le trigger, l'erreur partagée ci-dessus est déclenchée.

D'ailleurs, est-ce que ce bloc de code par défaut est nécessaire ou peut être supprimé ?

# Input bindings are passed in via param block. param($Timer) # Get the current universal time in the default string format. $currentUTCtime = (Get-Date).ToUniversalTime() # The 'IsPastDue' property is 'true' when the current function invocation is later than scheduled. if ($Timer.IsPastDue) { Write-Host "PowerShell timer is running late!" } # Write an information log with the current time. Write-Host "PowerShell timer trigger function ran! TIME: $currentUTCtime"

Answer 1

The issue is not inside my script ! My script works. I tried with a simple test script, I kept the default script generated by Azure and added one Write-Host :

# Input bindings are passed in via param block.
param($Timer)

# Get the current universal time in the default string format.
$currentUTCtime = (Get-Date).ToUniversalTime()

# The 'IsPastDue' property is 'true' when the current function invocation is later than scheduled.
if ($Timer.IsPastDue) {
    Write-Host "PowerShell timer is running late!"
}

# Write an information log with the current time.
Write-Host "PowerShell timer trigger function ran! TIME: $currentUTCtime"

Write-Host "Function works"

I kept the default trigger generated by Azure (function.json)

{
  "bindings": [
    {
      "name": "Timer",
      "type": "timerTrigger",
      "direction": "in",
      "schedule": "0 */5 * * * *"
    }
  ]
}

And it does not work ! I get this log :

2025-06-03T07:20:26Z [Information] Executing 'Functions.TimerTrigger1' (Reason='This function was programmatically called via the host APIs.', Id=04ec27a3-8ab9-4e65-bd33-d55f12f9250d)

2025-06-03T07:20:26Z [Error] Executed 'Functions.TimerTrigger1' (Failed, Id=04ec27a3-8ab9-4e65-bd33-d55f12f9250d, Duration=12ms)

By editing the schedule ONLY and defining " */59 * * * * * ", it works !

2025-06-03T07:37:03Z [Information] Executing 'Functions.TimerTrigger1' (Reason='This function was programmatically called via the host APIs.', Id=80095f9d-a513-45cc-bb2c-105b9e3eb9ce)

2025-06-03T07:37:03Z [Verbose] Sending invocation id: '80095f9d-a513-45cc-bb2c-105b9e3eb9ce

2025-06-03T07:37:03Z [Verbose] Posting invocation id:80095f9d-a513-45cc-bb2c-105b9e3eb9ce on workerId:35896789-7614-4118-bf66-197868c1a7df

2025-06-03T07:37:03Z [Information] INFORMATION: PowerShell timer trigger function ran! TIME: 06/03/2025 07:37:03

2025-06-03T07:37:03Z [Information] INFORMATION: Function works

2025-06-03T07:37:03Z [Information] Executed 'Functions.TimerTrigger1' (Succeeded, Id=80095f9d-a513-45cc-bb2c-105b9e3eb9ce, Duration=32ms)

The issue is not in the script ... I don't understand why this behavior ...

Could it be related to my App Service Plan ? I'm using "Y1", and a "Consumption" hosting plan.

Answer 2

Smith Pham 2,795 Conseiller(ère) indépendant(e)

Dear Guillaume

To run your Azure PowerShell Function every 5 minutes, use this CRON expression:


Copy
0 */5 * * * *

Don't use */5 * * * * — it's incorrect in Azure.

You're using the wrong format. Azure requires 6 fields, starting with seconds.

Guillaume THIERY 0 Points de réputation

2025-06-02T08:12:44.5966667+00:00
Hello,

I'm already using the right CRON expression on 6 fields.

0 */5 * * * * --> This does not work. I can apply the trigger but the script fails with this error :

[Error] Executed 'Functions.ps-test' (Failed, Id=989e2385-f915-4f15-bda3-527c03ec353e, Duration=2ms)

/59 * * * * * --> This works but runs every 59 seconds, that is too frequent.

How can I activate the execution logs of the Function App to investigate ?
Smith Pham 2,795 Points de réputation Conseiller(ère) indépendant(e)

2025-06-02T08:17:34.79+00:00
Hi Guillaume,

You're absolutely right to use 6 fields for Azure Functions CRON expressions — Azure requires the format:

{second} {minute} {hour} {day} {month} {day-of-week}

So to run every 5 minutes, the correct expression is:

0 */5 * * * *

If it fails, the issue is not with the CRON expression itself — it's likely inside your script/function.

The CRON is valid and should trigger your Azure Function correctly every 5 minutes at 0 seconds (e.g., 12:00:00, 12:05:00, 12:10:00, etc.).