CallHttpAsync HttpRetryOptions not retrying on .NET isolated worker #3444
Unanswered
m-spurgeon
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using .NET isolated Azure Durable Functions and calling CallHttpAsync, with HttpRetryOptions configured, from my orchestrator. The HTTP call fails with a retryable status (e.g. 503), but the orchestration does not retry, it fails after a single attempt.
Example:
The error we are getting is below, but a retry isn't triggered from this.
Is there any reason this wouldn't be working with Isolated? The equivalent code had been working as expected using in-process.
Beta Was this translation helpful? Give feedback.
All reactions