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

parentInstanceId not populated for sub-orchestrations #227

Open
epDugas opened this issue Dec 11, 2024 · 2 comments
Open

parentInstanceId not populated for sub-orchestrations #227

epDugas opened this issue Dec 11, 2024 · 2 comments
Labels
P2 Priority 2

Comments

@epDugas
Copy link
Contributor

epDugas commented Dec 11, 2024

The parentInstanceId appears to not be populated for sub-orchestrations.
DFMon is deployed as an Azure Function App, Durable Function storage provider is Azure Storage.
The sub-orchestrations are showing correctly under their parent orchestration's details.

@scale-tone
Copy link
Contributor

@epDugas , I'm not observing this, so can you please add more details?

Which version? InProc or Isolated? Was it always like that or started recently? Does it work locally/in VsCode?

The default routine for fetching parentInstanceIds is here, btw.

@epDugas
Copy link
Contributor Author

epDugas commented Dec 16, 2024

@scale-tone, thanks, will check out the default routine.

Additional detail:
Version 6.6
Isolated
Don't know, just used a sub-orc for the first time and observed it.
Same issue in VsCode.

@AnatoliB AnatoliB added P2 Priority 2 and removed Needs: Triage 🔍 labels Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority 2
Projects
None yet
Development

No branches or pull requests

3 participants