Skip to content

Commit 968d487

Browse files
authored
incorporate PR feedback
1 parent 7088a45 commit 968d487

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/azure-functions/durable/durable-functions-instance-management.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1011,8 +1011,7 @@ async def main(req: func.HttpRequest, starter: str, instance_id: str) -> func.co
10111011
If you have an orchestration failure for an unexpected reason, you can *rewind* the instance to a previously healthy state by using an API built for that purpose.
10121012

10131013
> [!NOTE]
1014-
> This API is not intended to be a replacement for proper error handling and retry policies. Rather, it is intended to be used only in cases where orchestration instances fail for unexpected reasons. For more information on error handling and retry policies, see the [Error handling](durable-functions-error-handling.md) article.
1015-
> The `rewind` API is only meant to be used against `Failed` or `Terminated` orchestrators. Orchestrators in other states such as `Running`, `Pending`, `Suspended`, `Completed` cannot be be "rewinded".
1014+
> This API is not intended to be a replacement for proper error handling and retry policies. Rather, it is intended to be used only in cases where orchestration instances fail for unexpected reasons. Orchestrations in other states such as `Running`, `Pending`, `Suspended`, `Completed`, and `Terminated` cannot be "rewound". For more information on error handling and retry policies, see the [Error handling](durable-functions-error-handling.md) article.
10161015
10171016
Use the `RewindAsync` (.NET) or `rewind` (JavaScript) method of the [orchestration client binding](durable-functions-bindings.md#orchestration-client) to put the orchestration back into the *Running* state. This method will also rerun the activity or sub-orchestration execution failures that caused the orchestration failure.
10181017

0 commit comments

Comments
 (0)