aws-amplify / aws-amplify/amplify-hosting
UI stuck in "Provisioning app backend", "Deleting backed env" and "Creating backed env" loop
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
### How did you install the Amplify CLI?
npm
### If applicable, what version of Node.js are you using?
v15.14.0
### Amplify CLI Version
4.52.0
### What operating system are you using?
Mac
### Amplify Categories
api
### Amplify Commands
push
### Describe the bug
The only thing I did was change a type from String to an enum type, in one of the models. and did amplify push --y
did similar things so many times this week but never faced an issue.
The cli gets stuck at :
```
✔ Generated GraphQL operations successfully and saved at src/graphql
⠼ Updating resources in the cloud. This may take a few minutes...
GraphQL schema compiled successfully.
```
upon going to the amplify console online, I see:

on refresh:

on refresh:

then it goes back to completed, and never finishes.
The change is deployed to AppSync, since I see it when I run my mutation.
everything is fine but the backend is stuck and not allowing any more changes since its stuck in some unknown state.
If I use a separate terminal instance and run amplify push with a small change, it throws:
`Failed to create models in the cloud: ValidationException - An error occurred while processing your request: ValidationException: There is already a pending job for the requested appId: dckq06nq2cy6m and backendEnvironmentName: dev, wait for it to complete before creating a new job.`
### Expected behavior
cli finishes and backed is in completed state.
### Reproduction steps
unable to reproduce
### GraphQL schema(s)
```graphql
# Put schemas below this line
```
### Log output
```
# Put your logs below this line
```
### Additional information
_No response_
Contributor guide
Research direction
Start with the `amplify push` entry point and the reported AppSync/backend-environment provisioning flow, using the pending-job ValidationException as the initial symptom. Reproduction is currently unavailable and no logs or schema are provided; done means the CLI finishes and the backend environment returns to completed so another push can run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, graphql, node.js
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100