File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -16,7 +16,7 @@ You should see output indicating that the `ResourcePoolWorkflow` serialized acce
1616
1717You can query the set of current resource resource holders with:
1818
19- tctl wf query -w resource_pool --qt get_current_holders
19+ temporal workflow query --workflow-id resource_pool --name get_current_holders
2020
2121# Other approaches
2222
@@ -41,7 +41,7 @@ Temporal's durable execution guarantees, this can only happen if:
4141
4242If a leak were to happen, you could discover the identity of the leaker using the query above, then:
4343
44- tctl wf signal -w resource_pool --name release_resource --input '{ "release_key": "<the key from the query above>" }
44+ temporal workflow signal --workflow-id resource_pool --name release_resource --input '{ "release_key": "<the key from the query above>" }'
4545
4646Performance: A single ResourcePoolWorkflow scales to tens, but not hundreds, of request/release events per second. It is
4747best suited for allocating resources to long-running workflows. Actual performance will depend on your temporal server's
You can’t perform that action at this time.
0 commit comments