Serverless Stack

Hey, I keep having this issue intermittently and my usual workaround is to just go into the console and delete a stack, but here is the issue, i'm wondering if there's a better, more time efficient, fix

I deployed stack 1 that attempted to stand up a rest api, but there was a conflict with stack 2 that had an api under a similar name, so stack 1  was rolled back and all the resourced it tried to stand up were deleted. I'm in the process of removing stack 2, and I'm now trying to deploy stack 1. On AWS console it's status is 'ROLLBACK_COMPLETE' and all resources under the stack have either status 'DELETE_COMPLETE' or 'DELETE_SKIPPED', thus, my expected behavior when deploying stack 1 is that it would re-attempt to stand up the resources it initially failed to create. However, when I run `yarn deploy`  the status of my stack in the console is `Status: no changes`

note: I've also tried doing a `yarn run build` before attempting to deploy

I was just now able to resolve the issue by adding an inconsequential env var to one of the lambas on stack 1. I can't help but feel that there's a better way to work around this issue though

Hi <@U02RHMGU78C>, this should be fixed. Can you update SST to the latest version (ie. v0.65.2) and see if the issue persist?