You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I am trying to create a durable function flow that basically creates a timer that triggers an orchestrator. According to the logs when i run "func start". Both triggers are generated appropriately and the first (the scheduler) executes successfully and creates an entry in the instances table for the orchestration with status of "Pending". However, this task never gets picked up and executed by the worker. Am I doing something wrong or is this a bug with the framework?
As a note I am running on MAC arm64. These are the logs of my run
Found Python version 3.12.10 (python3).
Azure Functions Core Tools
Core Tools Version: 4.0.7030 Commit hash: N/A +bb4c949899cd5659d6bfe8b92cc923453a2e8f88 (64-bit)
Function Runtime Version: 4.1037.0.23568
[2025-05-23T13:19:14.067Z] 0.00s - Debugger warning: It seems that frozen modules are being used, which may
[2025-05-23T13:19:14.068Z] 0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
[2025-05-23T13:19:14.068Z] 0.00s - to python to disable frozen modules.
[2025-05-23T13:19:14.068Z] 0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
[2025-05-23T13:19:14.105Z] Worker process started and initialized.
Functions:
orchestrator: orchestrationTrigger
scheduler: timerTrigger
For detailed output, run func with --verbose flag.
[2025-05-23T13:19:14.230Z] Executing 'Functions.scheduler' (Reason='Timer fired at 2025-05-23T09:19:14.2122820-04:00', Id=0223ecf0-c40a-41cf-9f4d-0cf83010113e)
[2025-05-23T13:19:14.231Z] Trigger Details: UnscheduledInvocationReason: RunOnStartup
[2025-05-23T13:19:14.244Z] devstoreaccount1: This partition already exists in the partition table.
[2025-05-23T13:19:14.246Z] Durable task hub worker is starting
[2025-05-23T13:19:14.262Z] TaskOrchestrationDispatcher-554228f57fe54e6f8632e5d51dd5d74c-0: Starting dispatch loop
[2025-05-23T13:19:14.263Z] TaskActivityDispatcher-b5ba53ee9a5d4014876e48175fdd3182-0: Starting dispatch loop
[2025-05-23T13:19:14.263Z] Durable task hub worker started successfully after 16ms
[2025-05-23T13:19:14.264Z] TaskActivityDispatcher-b5ba53ee9a5d4014876e48175fdd3182-0: Fetching next work item. Current active work-item count: 0. Maximum active work-item count: 10. Timeout: 30s
[2025-05-23T13:19:14.265Z] TaskOrchestrationDispatcher-554228f57fe54e6f8632e5d51dd5d74c-0: Fetching next work item. Current active work-item count: 0. Maximum active work-item count: 100. Timeout: 30s
[2025-05-23T13:19:14.283Z] discovery-applease: Attempting to acquire app lease
[2025-05-23T13:19:14.297Z] discovery-applease: Successfully acquired app lease
[2025-05-23T13:19:14.314Z] Started the background partition manager loop to acquire and balance partitions.
[2025-05-23T13:19:14.315Z] discovery-applease: Starting background renewal of app lease with interval: 00:00:25.
[2025-05-23T13:19:14.315Z] discovery-applease: Starting app lease renewal with token 811c9dc5-0000-0000-0000-000000000000
[2025-05-23T13:19:14.322Z] discovery-applease: app lease renewal with token 811c9dc5-0000-0000-0000-000000000000 succeeded
[2025-05-23T13:19:14.323Z] Fetched instance status for ab0b67bae40b468594fe512234d525f6
[2025-05-23T13:19:14.329Z] devstoreaccount1: Successfully acquired lease
[2025-05-23T13:19:14.329Z] devstoreaccount1: Started listening for messages on queue devstoreaccount1.
[2025-05-23T13:19:14.329Z] devstoreaccount1: lease renewal with token succeeded
[2025-05-23T13:19:14.389Z] devstoreaccount1: No new messages were found - backing off
[2025-05-23T13:19:14.391Z] Sending [ExecutionStarted] message to devstoreaccount1 for instance 'ab0b67bae40b468594fe512234d525f6'
[2025-05-23T13:19:14.407Z] ab0b67bae40b468594fe512234d525f6: Updated Instances table and set the runtime status to 'Pending'
[2025-05-23T13:19:14.416Z] Started orchestration with ID = ab0b67bae40b468594fe512234d525f6
[2025-05-23T13:19:14.426Z] Executed 'Functions.scheduler' (Succeeded, Id=0223ecf0-c40a-41cf-9f4d-0cf83010113e, Duration=210ms)
[2025-05-23T13:19:19.091Z] Host lock lease acquired by instance ID '00000000000000000000000092F99DAC'.
[2025-05-23T13:19:24.344Z] devstoreaccount1: lease renewal with token succeeded
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello! I am trying to create a durable function flow that basically creates a timer that triggers an orchestrator. According to the logs when i run "func start". Both triggers are generated appropriately and the first (the scheduler) executes successfully and creates an entry in the instances table for the orchestration with status of "Pending". However, this task never gets picked up and executed by the worker. Am I doing something wrong or is this a bug with the framework?
As a note I am running on MAC arm64. These are the logs of my run
Beta Was this translation helpful? Give feedback.
All reactions