Skip to content

.Net: Bug: Activating ProcessStep function does not work if multiple functions implemented #11760

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

Open
ddobric opened this issue Apr 27, 2025 · 4 comments
Assignees
Labels
bug Something isn't working .NET Issue or Pull requests regarding .NET code

Comments

@ddobric
Copy link
Contributor

ddobric commented Apr 27, 2025

Hi all,

I'm using the C# process framework. Have implemented a ProcessStep class, which has two functions.
Getting the following error:

Image

I have activated the function by specifying the name:

Image

How to repro?

Implement a class with two functions:

Image

@ddobric ddobric added the bug Something isn't working label Apr 27, 2025
@markwallace-microsoft markwallace-microsoft added .NET Issue or Pull requests regarding .NET code triage labels Apr 27, 2025
@github-actions github-actions bot changed the title Bug: Activating ProcessStep function does not work if multiple functions implemented .Net: Bug: Activating ProcessStep function does not work if multiple functions implemented Apr 27, 2025
@feiyun0112
Copy link
Contributor

Please provide the complete code

I guess the OnFunctionResult method did not pass in the specified functionName
https://github.com/microsoft/semantic-kernel/blob/main/dotnet/src/Experimental/Process.Core/ProcessStepBuilder.cs#L53

@ddobric
Copy link
Contributor Author

ddobric commented Apr 30, 2025

I'm not sure about OnFunctionResult. I'm invoking the function on the input event.

Image

Hope this helps.

@feiyun0112
Copy link
Contributor

Image

I'm not sure about OnFunctionResult. I'm invoking the function on the input event.

Image

Hope this helps.

@ddobric
Copy link
Contributor Author

ddobric commented May 19, 2025

Whatever the right event might be, the framework MUST NOT THROW in this case. The argument functionName specifies the function which should be invoked. @feiyun0112 I'm not looking for a workaround, which might be a different event or simply commenting out the second function.

I guess this is the bug, which needs to be fixed or some special feature, who knows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working .NET Issue or Pull requests regarding .NET code
Projects
None yet
Development

No branches or pull requests

5 participants