Skip to content

Conversation

@jamesgibbons92
Copy link
Collaborator

@jamesgibbons92 jamesgibbons92 commented Jan 22, 2026

closes #6345

The timeout timer was being recreated every time a deployment completion event happened as the timer was initilised within the event loop, this means if you are changing stack code and deploying within the ~50 minute window, then the timer would reset, even though the dev task is still running.

To reproduce the original issue:

set timeout := time.Seconds * 30

With a long running task, e.g.:

   new sst.x.DevCommand("Hi", {
      dev: {
        command: "sleep 60",
      },
    });

Save / touch the sst.config.ts file, which causes a deployment from the watcher.

Note that the timeout and restart never occurs, and the command eventually exits.

With the change in this PR, this issue is resolved and the dev command restarts as expected after 30 seconds, regardless of deployments completing.

@niss36
Copy link

niss36 commented Jan 30, 2026

Would love to see this merged! It's really annoying having to remember to restart sst every hour or so

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ExpiredTokenException in sst dev after ~60 minutes

2 participants