-
Notifications
You must be signed in to change notification settings - Fork 50
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
Failed: node exited with code 1 #543
Labels
Debuggability
Experience problem debugging code.
Needs: Attention 👋
P3
Priority 3
programming model 🚀
Comments
@shyamal890 - could you provide a minimal repro of the problem? |
lilyjma
added
Needs: Author Feedback
Waiting for the author of the issue to respond to a question
P3
Priority 3
and removed
Needs: Triage 🔍
labels
Sep 26, 2023
Actually it's an extensive implementation and hence provided the instance id of the orchestration, so you could check the logs directly. |
microsoft-github-policy-service
bot
added
Needs: Attention 👋
and removed
Needs: Author Feedback
Waiting for the author of the issue to respond to a question
labels
Sep 27, 2023
lilyjma
added
Debuggability
Experience problem debugging code.
programming model 🚀
labels
Jan 5, 2024
I guess this is still unresolved. I'm experiencing the same situation on my durable function calling an activity that fails without any other information other than the stack trace. Here is the stack trace:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Debuggability
Experience problem debugging code.
Needs: Attention 👋
P3
Priority 3
programming model 🚀
Describe the bug
Functions are randomly failing without any details on the error that caused the failure.
Investigative information
If deployed to Azure App Service
To Reproduce
A long running operation
Expected behavior
It shouldn't have crashed and if it did, there should be an error to understand what caused the error
Actual behavior
Here's the output of get status
Known workarounds
None at this time
Additional context
The text was updated successfully, but these errors were encountered: