Cannot get state for specific executionId
See original GitHub issueHello, reaching out for help
When trying to use the Task<OrchestrationState> GetOrchestrationStateAsync(string instanceId, string executionId)
on an eternal orchestration, I do not receive the orchestrationstate with the correct executionId. It seems that what is returned is the latest execution for the orchestration and I would like to verify if this is unexpected behavior or not.
It would be great to understand if it is possible to query for a specific executionId of an orchestration or if that is not tracked.
In addition, I noticed that when trying to get the history for any executions besides the latests, the history would return to be empty. Is the history for previous executions saved?
Any help and advice is appreciated, Thanks!
Issue Analytics
- State:
- Created 7 months ago
- Comments:7
Top Results From Across the Web
State/Execution ID in SSIS
I have a problem with multiple executions of the same SSIS package. I would like to allow parallel executions each of which handles...
Read more >StartExecution - AWS Step Functions
Starts a state machine execution. ... Step Functions doesn't associate state machine executions that you start with an unqualified ARN with a version....
Read more >Article: How to Cancel/Stop a Pending Process Execution
Sometimes there are pending executions in process reporting, either the process is taking too long or it is stuck somewhere in the process....
Read more >Get Workflow Execution State | VMware Cloud Director ...
Retrieves the current state for a requested workflow run.
Read more >SSIS package does not run when called from a job step
Therefore, the SQL Server Agent job step can load and start to run the job step, but the package fails because it cannot...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s not configurable. The only workaround I can suggest is to rely on logging.
Whether you can do this depends on how the orchestration state is stored in the task hub, which is dependent on the implementation of
IOrchestrationService
. If that implementation stores each execution ID separately, then yes in theory you could write aIOrchestrationServiceClient
that fetches orchestration state for specific execution IDs.I don’t understand the question - the implementation of
IOrchestrationServiceClient
is unrelated to how orchestration state is managed at runtime or how continue-as-new works.Assuming that the
IOrchestrationService
implementation you’re relying on doesn’t keep a history of old execution IDs, you may need to rely on logging and tracing to debug issues for orchestrations that use continue-as-new.