get_status(instance_id) - runtime_status is not up to date about azure-functions-durable-python HOT 4 CLOSED

@DariaSliusar - It would be good to triple check that the portal is also reporting the correct information. If you go to your storage account with the portal's storage explorer, and look at the instances table for your takshub. In there, does the orchestrator's instanceID also report "Completed"?

from azure-functions-durable-python.

@davidmrdavid, thanks for your reply. On the portal, I was checking the status by Function App -> function_name -> Orchestrations. The status there was 'Completed', when client.get_status = 'Running'.

from azure-functions-durable-python.

Thanks @DariaSliusar. The portal's status reports have been known to be unreliable at times, as they don't check 'real' the "source truth" (which is the Instances table in your storage account) and instead check the telemetry to try to infer if an orchestrator is "Running" or "Completed". For that reason, would you be able to triple check the Instances table for your task hub in your storage account and see if the entry for your instanceID is indeed completed?

If your TaskHub is named "MyTaskHub", then the table's name would my "MyTaskHubInstances"

from azure-functions-durable-python.

Thanks for the additional information provided. As was realized, the status is updated asynchronously and may not immediately reflect the most recent state of the orchestration, which is due to the distributed nature of the Durable Task Framework, which Azure Durable Functions is built upon.

from azure-functions-durable-python.