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
I have three issues here, but let's start with this one before uncovering the others.
When running the orchestration, seemingly not all things run as they should, but I get no exceptions or errors in the output.
My code is a bit unconventional because I'm trying to implement complex flows with durable functions, so I want to create functions dynamically.
[2024-07-24T09:24:00.599Z] Worker process started and initialized.
[2024-07-24T09:24:05.664Z] Host lock lease acquired by instance ID '0000000000000000000000001DA5AB02'.
[2024-07-24T09:24:07.916Z] Executing 'Functions.t1_http' (Reason='This function was programmatically called via the host APIs.', Id=e502f88a-64f6-48cb-bdba-e46c326c6ef0)
[2024-07-24T09:24:08.195Z] Executed 'Functions.t1_http' (Succeeded, Id=e502f88a-64f6-48cb-bdba-e46c326c6ef0, Duration=292ms)
[2024-07-24T09:24:08.343Z] Executing 'Functions.t1' (Reason='(null)', Id=4a587992-146f-461c-85ea-9c8140a9cb43)
[2024-07-24T09:24:08.392Z] [tasks] running all tasks
[2024-07-24T09:24:08.392Z] [orchestrator] Running
[2024-07-24T09:24:08.421Z] Executed 'Functions.t1' (Succeeded, Id=4a587992-146f-461c-85ea-9c8140a9cb43, Duration=89ms)
log no. 1
[2024-07-24T09:30:24.166Z] Executing 'Functions.t1_http' (Reason='This function was programmatically called via the host APIs.', Id=0c5d0e54-1934-474c-bf9b-270e9da42b6d)
[2024-07-24T09:30:24.254Z] Executed 'Functions.t1_http' (Succeeded, Id=0c5d0e54-1934-474c-bf9b-270e9da42b6d, Duration=93ms)
[2024-07-24T09:30:24.267Z] Executing 'Functions.t1' (Reason='(null)', Id=737248a6-c111-4cac-a5df-e316371f679d)
[2024-07-24T09:30:24.283Z] [orchestrator] Running
[2024-07-24T09:30:24.283Z] [tasks] running all tasks
[2024-07-24T09:30:24.293Z] Executed 'Functions.t1' (Succeeded, Id=737248a6-c111-4cac-a5df-e316371f679d, Duration=29ms)
There are two things wrong in the above logs. First off, the logs coming out are not deterministic or at least there's some race condition happening as one the [orchestrator] and the [tasks] log order is mixed up between no. 1 and 2. I don't see how this could happen as this is run in the same thread.
But more importantly, the logging commands below don't run and there's no exception. So I'm wondering, does the code run and the logs don't appear in my console or, what I think is happening, is the orchestrator doesn't fully run because there are errors in the activity functions and something breaks.
🤔 Expected behavior
Either I get an exception or all the code runs.
☕ Steps to reproduce
Run func start locally on my code and visit http://localhost:7071/api/t1, then check the logs.
The text was updated successfully, but these errors were encountered:
I have three issues here, but let's start with this one before uncovering the others.
When running the orchestration, seemingly not all things run as they should, but I get no exceptions or errors in the output.
My code is a bit unconventional because I'm trying to implement complex flows with durable functions, so I want to create functions dynamically.
function_app.py
requirements.txt
log no. 1
log no. 1
There are two things wrong in the above logs. First off, the logs coming out are not deterministic or at least there's some race condition happening as one the
[orchestrator]
and the[tasks]
log order is mixed up between no. 1 and 2. I don't see how this could happen as this is run in the same thread.But more importantly, the logging commands below don't run and there's no exception. So I'm wondering, does the code run and the logs don't appear in my console or, what I think is happening, is the orchestrator doesn't fully run because there are errors in the activity functions and something breaks.
🤔 Expected behavior
Either I get an exception or all the code runs.
☕ Steps to reproduce
Run
func start
locally on my code and visithttp://localhost:7071/api/t1
, then check the logs.The text was updated successfully, but these errors were encountered: