An error occurred during the push operation: Cannot iteratively rollback as the following step does not contain a previousMetaKey: {"status":"DEPLOYING"}

[alzotov]

Before opening, please confirm:

• [X] I have checked to see if my question is addressed in the FAQ.
• [X] I have searched for duplicate or closed issues.
• [X] I have read the guide for submitting bug reports.
• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id

d3oybpl8qpijc0 --envName stage

Region

ap-norteast-1

Amplify Console feature

No response

Describe the bug

amplify push fails with error: An error occurred during the push operation: Cannot iteratively rollback as the following step does not contain a previousMetaKey: {"status":"DEPLOYING"}

(I had once this command results with unusual status like: deploying in the cloud... - instead of usual digest of app params)

Expected behavior

{"status":"DEPLOYING"} must be temporary status ending up with some final status

Reproduction steps

amplify push

(I had once this command results with unusual status like: deploying in the cloud... - instead of usual digest of app params)

Build Settings

No response

Additional information

No response

[github-actions[bot]]

Hi :wave:, thanks for opening! While we look into this...

If this issue is related to custom domains, be sure to check the custom domains troubleshooting guide to see if that helps. Also, there is a more general troubleshooting FAQ that may be helpful for other questions.

Lastly, please make sure you've specified the App ID and Region in the issue!

[sachscode]

Hi @alzotov

1. Could you please provide more details as to which commands did you execute before you got to this state.
2. Do you have any manual changes in the cloud ?
3. Could you please provide the file-names of all the files in your deployment bucket.

[mostafasany]

it happens to me as well, I was deploying using amplify push and the machine crashed, then I tried amplify push --force and amplify push --iterative-rollback but give me this error

[simsek97]

This happens when your deployment was interrupted or aborted unexpectedly due to a network error or something like that. Amplify CLI doesn't have any power to fix this issue but you can work around by following the steps below.

• Find your deployment bucket in the team-provider-info.json file. env -> awscloudformation -> DeploymentBucketName will give you the bucket name.
• Go to Amazon S3 console and search for the bucket.
• Inside the bucket, there should be a file called deployment-state.json. Delete this file.
• Run amplify push or amplify push --force again.

[david-startinvest]

god bless you solved the problem

[JeHwanYoo]

This happens when your deployment was interrupted or aborted unexpectedly due to a network error or something like that. Amplify CLI doesn't have any power to fix this issue but you can work around by following the steps below.

• Find your deployment bucket in the team-provider-info.json file. env -> awscloudformation -> DeploymentBucketName will give you the bucket name.
• Go to Amazon S3 console and search for the bucket.
• Inside the bucket, there should be a file called deployment-state.json. Delete this file.
• Run amplify push or amplify push --force again.

You saved my life 👍

[JeHwanYoo]

If the aws doesn't take this issue seriously, amplify can only be used by very experienced DB architects. If you can set the PK and Index at once without making a single mistake, you may not face this problem...