Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AcceptedAtRouteResult in isolated process #10451

Open
MarioMajcicaAtABNAMRO opened this issue Sep 6, 2024 · 0 comments
Open

AcceptedAtRouteResult in isolated process #10451

MarioMajcicaAtABNAMRO opened this issue Sep 6, 2024 · 0 comments

Comments

@MarioMajcicaAtABNAMRO
Copy link

We are moving from the inproc model to isolated process model. We are facing certain hiccups. One of the annoying ones is the following.

We do often return AcceptedAtRouteResult from our durable function. The following code sample works as expected in the inproc function:

return new AcceptedAtRouteResult(nameof(ServiceConnectionCreationGetStatus), new { orchestrationId }, response);

However, the same in isolated model throws an exception:

Result: Function 'ServiceConnectionCreate', Invocation id '5ba8911a-cc70-417c-826a-81d8e64cf349': An exception was thrown by the invocation.
Exception: System.InvalidOperationException: No route matches the supplied values.

Does anyone know how to make this work or and why is this now the behavior? I can't find anything in this regard in the documentation, and this is the only issues that seems relevant #10393

Any help would be appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant