[Feature] Ability to set custom status via DurableOrchestrationClient #1862
Replies: 3 comments
-
Can you go into more detail about why you might need custom status in your scenario? My initial reaction is that a runtime status value of "Pending" should be sufficient to communicate that the orchestration hasn't started yet. |
Beta Was this translation helpful? Give feedback.
-
I guess in my mind Pending didn't tell me that the orchestration had been successfully queued for execution. Also I was keying off the CustomStatus value and started hitting instances where it came back |
Beta Was this translation helpful? Give feedback.
-
It might be possible to do this if we make a change to the durable task framework. I'd like to hear if others would like a similar feature though. |
Beta Was this translation helpful? Give feedback.
-
In the following code:
I'd like to be able to set the custom status so calls to the GetStatus API can return better information while waiting for the orchestrator to pick up and begin execution.
Today I can only set custom status off
DurableOrchestrationContext
which means I have to wait for the orchestrator to start running before I can return anything meaningful.Beta Was this translation helpful? Give feedback.
All reactions