## TL;DR

Commenter tienpvse1 fixed it by resetting SST's state in S3: go to the sst-state bucket for your app, open the snapshots folder, download the latest snapshot from when SST was still working, and use that JSON to replace the state in your local app folder.

## Steps

1. What was reported:
Issue anomalyco/sst#4573 (closed, 48 comments): sst deploy (ion) gets interrupted every time with no error message. Verbose logs just stop partway through initializing the project. The reporter was following the aws-nextjs example and could not tell what was wrong, since nothing in the output pointed at a cause.

2. What works:
Community-verified hard reset. Commenter tienpvse1 fixed it by resetting SST's state in S3: go to the sst-state bucket for your app, open the snapshots folder, download the latest snapshot from when SST was still working, and use that JSON to replace the state in your local app folder. That forces a hard reset of the corrupted state and the deploy goes through. This is the fix to reach for when sst deploy dies silently and nothing in the verbose logs explains why, rather than recreating the whole stage.

## When to use

You are seeing this: What was reported: Issue anomalyco/sst#4573 (closed, 48 comments): sst deploy (ion) gets interrupted every time with no error message. Use this skill when you run into "sst deploy interrupted with no error: hard-reset the state snapshot in S3".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.