@Sam-Fly yes i was able to login to the problematic sprite. Also updated the other as well. thanks for the reply.
2 Likes
I’m having this issue with one of my sprites. I rather desperately need it back and working by tomorrow. Any chance you could update mine? It’s stuck in a running state and I cannot connect or do anything else with it.
Having this issue too. sprite ls shows the sprite as running, but sprite c and sprite exec time out. Existing connections to the sprite stop responding. Eventually the sprite starts responding again. This has happened 2 or 3 separate times today already. To be fair this is on an older version of sprites. I just created a new sprite and I’ll see how that goes
@mt1 I’ve upgraded all sprites in your org. Should be all set but if you still see issues lmk the name of the specific Sprite.
@njbotkin same for your sprites, I’ve upgraded them now as well. Any issues let us know
We’re also hitting this on our platform — we run persistent sprites as agent backends (auto-sleep/wake on HTTP). One of our sprites went cold and never came back — all HTTP requests return 502, management API times out, sprite exec fails with websocket 502.
The sprite was created recently so it may be on an older version. @Sam-Fly could you upgrade sprites in our org? The stuck one is showing the same symptoms others have described — no recovery after 24+ hours.
We’ve built a destroy-and-recreate workaround on our end, but a management API endpoint to force-reboot a stuck sprite would be really valuable for production use cases. Would also love automatic version updates when they’re ready.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.