All Functions within a Function App Running on CRON Change - Duplicated Transaction Logs

Hello

I already have them separated and even when the CRON expression are set to run at different times, one timer kicking off runs them all.

Let me try and lay it out in a different way to see if I can understand you, thanks for your patience.

We'll use a single function for now: GraceWeekly1400

has the following two files:

The first 21 lines of the _init___py file looks like this:

import datetime
import logging
import azure.functions as func
import requests
from requests.utils import parse_header_links
import pandas as pd
from dateutil import parser
import pytz
import jsonpickle
import pyodbc
from sqlalchemy import create_engine, Integer, Date, String, Float, text, DateTime, Time, Boolean
import time

def main(churchmetricstimer: func.TimerRequest) -> None:
    utc_timestamp = datetime.datetime.utcnow().replace(
        tzinfo=datetime.timezone.utc).isoformat()

    if churchmetricstimer.past_due:
        logging.info('The timer is past due!')

    logging.info('Python timer trigger function ran at %s', utc_timestamp)

The function.json file within that function looks like this:

{
  "scriptFile": "__init__.py",
  "bindings": [
    {
      "name": "churchmetricstimer",
      "type": "timerTrigger",
      "direction": "in",
      "schedule": "0 0 20 * * 1"
    }
  ]
}

The other function GraceWeekly_PC has it's own files:

init__.py

import requests
import base64
import pandas as pd
from datetime import datetime
import pytz
import time
import datetime
import pyodbc
from sqlalchemy import create_engine, Integer, Date, String, Float, text, DateTime, Boolean, Time
import datetime 
import logging
import azure.functions as func

def main(planningcentertimer: func.TimerRequest) -> None:
    utc_timestamp = datetime.datetime.utcnow().replace(
        tzinfo=datetime.timezone.utc).isoformat()

    if planningcentertimer.past_due:
        logging.info('The timer is past due!')

    logging.info('Python timer trigger function ran at %s', utc_timestamp)

and it's own function.json file

{
  "scriptFile": "__init__.py",
  "bindings": [
    {
      "name": "planningcentertimer",
      "type": "timerTrigger",
      "direction": "in",
      "schedule": "0 0 20 * * 1"
    }
  ]
}

Yet even though they are separate if I can only one to run every hour they both run.

Is the fact that both .py files are named init.py causing the issue?

I renamed my functions, their .py files and updated the functions.json files so the "scriptfile": pointed towards the appropriate .py file, so it would be more clear for this conversation and the function app.

It still ran both functions even though I only changed one of them to run at 55 minutes past the hour.

Function: GraceWeekly_CM

.py file is now named: GraceWeeklyChurchMetrics.py

import datetime
import logging
import azure.functions as func
import requests
from requests.utils import parse_header_links
import pandas as pd
from dateutil import parser
import pytz
import jsonpickle
import pyodbc
from sqlalchemy import create_engine, Integer, Date, String, Float, text, DateTime, Time, Boolean
import time

def main(churchmetricstimer: func.TimerRequest) -> None:
    utc_timestamp = datetime.datetime.utcnow().replace(
        tzinfo=datetime.timezone.utc).isoformat()

    if churchmetricstimer.past_due:
        logging.info('The timer is past due!')

    logging.info('Python timer trigger function ran at %s', utc_timestamp)

the function.json file

{
  "scriptFile": "GraceWeeklyChurchMetrics.py",
  "bindings": [
    {
      "name": "churchmetricstimer",
      "type": "timerTrigger",
      "direction": "in",
      "schedule": "0 55 * * * *"
    }
  ]
}

Function: GraceWeekly_PC

.py file now named GracePlanningCenter.py

import requests
import base64
import pandas as pd
from datetime import datetime
import pytz
import time
import datetime
import pyodbc
from sqlalchemy import create_engine, Integer, Date, String, Float, text, DateTime, Boolean, Time
import datetime 
import logging
import azure.functions as func

def main(planningcentertimer: func.TimerRequest) -> None:
    utc_timestamp = datetime.datetime.utcnow().replace(
        tzinfo=datetime.timezone.utc).isoformat()

    if planningcentertimer.past_due:
        logging.info('The timer is past due!')

    logging.info('Python timer trigger function ran at %s', utc_timestamp)

function.json

{
  "scriptFile": "GracePlanningCenter.py",
  "bindings": [
    {
      "name": "planningcentertimer",
      "type": "timerTrigger",
      "direction": "in",
      "schedule": "0 0 20 * * 1"
    }
  ]
}

One should run every hour at 55 minutes past the hour and the other once a week on Monday at 2000 UTC. Yet both functions are executed.

The request comes through as only the GraceWeekly_CM

Traces that I think may be helpful?

Executing 'Functions.GraceWeekly_CM' (Reason='Timer fired at 2024-03-31T01:55:00.0064964+00:00', Id=22172da9-4ffb-4a0b-a4c9-5860014b921d)

Initializing Warmup Extension.

Initializing Host. OperationId: 'e2c17ce8-74b0-4d90-bae5-195329c0683c'.

Host initialization: ConsecutiveErrors=0, StartupCount=1, OperationId=e2c17ce8-74b0-4d90-bae5-195329c0683c

ConcurrencyOptions

{

"DynamicConcurrencyEnabled": false,

"MaximumFunctionConcurrency": 500,

"CPUThreshold": 0.8,

"SnapshotPersistenceEnabled": true

}

ScaleOptions

{

"ScaleMetricsMaxAge": "00:02:00",

"ScaleMetricsSampleInterval": "00:00:10",

"MetricsPurgeEnabled": true,

"IsTargetScalingEnabled": true,

"IsRuntimeScalingEnabled": true

}

Loading functions metadata

Reading functions metadata (Custom)

1 functions found (Custom)

2 functions loaded

Generating 2 job function(s)

Found the following functions:

Host.Functions.GraceWeekly_CM

Host.Functions.GraceWeekly_PC

and the rest is history, both functions are executed when only one is supposed to.

Hi

Thank you for your feedback and comment. You have done a great job.

What I can see as a solution now on from your post:

1. Double-check that the file names and the references in function.json are correct and make sure there are no typos or discrepancies in the names.
2. Ensure that you've deployed the updated files correctly to your Function App. Please, crosscheck.
3. Check if there are any old versions of the files still present in your Function App environment that might be causing conflicts.
4. Restart your Function App to ensure that any cached configurations are cleared, and the changes are applied correctly.

Already soaring.

Good success.