-
Notifications
You must be signed in to change notification settings - Fork 0
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
bug stuck script #25
Comments
This thread may be helpful in diagnosing the problem (it sounds similar, scheduled but not started) https://community.temporal.io/t/activity-scheduled-but-not-started-need-help/4313/5 |
I noticed the following error in the script worker
This thread may offer useful advice to investigate: https://community.temporal.io/t/activity-timeout-and-temporal-server-connectivity-issue/8869/2 |
Seems like the heartbeat fixed that issue, but after updating I now have a new issue to content with...
This runs when running a sequence. My best guess is that it's too much information for Temporal's memory limit... |
It looks like that is a Node bug, which is said to be fixed in today's release 22.8.0 |
Down-graded to node@20 and everything is working. I'll install the update tomorrow and verify it's all working. |
Down-grading to node@20 until the update goes live. |
Installed node@20.17.0 in the package for now to ensure consistency of operation |
Latest installation is working without issue, I'm going to continue to use latest node build on the machine for now and will default back to local install if this occurs again for stability. Closing the issue. |
Every now and then jobs seem to get stuck on executing scripts. Re-starting the workers doesn't work. Doing a "Reset" command in temporal will re-submit the jobs and suddenly the post tasks will execute without issue. I suspect there's something wrong with how I'm scheduling the work, but will need to investigate and try to find a re-produceable scenario (difficult, as it typically requires a lot of frames to render to occur).
The text was updated successfully, but these errors were encountered: