- Newest
- Most votes
- Most comments
If rolling back a failed update also fails, you can select the "Continue Rollback" action (I guess you've already tried this). If this doesn't work then you can try it again but this time open the "Advanced" section and enter in a comma-separated list of LOGICAL (not physical) resource names to not attempt rollback on. Determine the resource names to use either from error messages or by going to the stack's Resources section and looking for resources in error state. Once rollback is complete, go and have a look at the resources that you skipped to check for any manual cleanup required.
Hello, when I do this, I get Currently in UPDATE_COMPLETE with reason: null for the resource when I do not skip it and "Nested stack resources can only be skipped when their embedded stack statuses are one of [DELETE_COMPLETE, DELETE_IN_PROGRESS, DELETE_FAILED]" when I select it to be skipped.
What can I do?
Relevant content
- asked 7 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thanks for the response. Tried everything but now with lambda version update error I am getting appsync API error too - The specified key does not exist, although the resolver files exists in the location where template suppose to save them. This failed my nested API stack and put my parent stack too in update rollback failed status. This also not allowing to make new update.