Sprite with actual work unresponsive, even checkpoints

My sprite “mason-c02860” is unresponsive for a while already:

$ sprite console -s mason-c02860
Error: failed to start sprite command: failed to connect: read tcp 192.168.88.247:55094->169.155.48.226:443: i/o timeout

Same with sessions or checkpoints.

$ sprite s ls -s mason-c02860
Error: failed to list sessions: failed to list sessions: Get "https://api.sprites.dev/v1/sprites/mason-c02860/exec": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

This happens quite often btw - I find the whole sprites thing to be quite unreliable.

Any change you can help? Would be nice to recover my work.

Thanks

Yeah, there have been two other posts like this in the forum already today:

https://community.fly.io/t/sprite-blocked-unresponsive/28384

https://community.fly.io/t/sprite-non-responsive/28383

The restart button in the dashboard really isn’t helping with this at all?


Hopefully their new CEO will clarify what sort of reliability actually is expected with these, in general. There have been people elsewhere in the forum openly asking whether Sprites are even intended for production, etc.

Thanks for the head up, did not know about the restart - that actually fixed it.

Wondering the same thing about production use.

I use sprites as a backend for my agent workflow - but exploring switching to microsandbox on a local home server.

Thanks again!

I just found out about the restart button but it’s also not working