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.

Sign up for GitHub

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

Jump to bottom

Processes: Process event forwarding #9553

Closed
alliscode opened this issue Nov 5, 2024 · 2 comments
Closed

Processes: Process event forwarding #9553

alliscode opened this issue Nov 5, 2024 · 2 comments
Labels
processes sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) stale Issue is stale because it has been open for 90 days with no activity

Comments

@alliscode
Copy link
Member

Processes should be able to forward an internal event to an external event with a different event Id. This would allow a process to maintain a stable external contract even if the steps within the process are changing.
@alliscode alliscode removed the triage label Nov 5, 2024
@evchaki evchaki added the sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) label Nov 5, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 4, 2025

This issue is stale because it has been open for 90 days with no activity.

@github-actions github-actions bot added the stale Issue is stale because it has been open for 90 days with no activity label Feb 4, 2025
@github-actions GitHub Actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
processes sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) stale Issue is stale because it has been open for 90 days with no activity
Projects
Semantic Kernel
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alliscode @evchaki @markwallace-microsoft