amplify-cli: CLI hangs on push after schema change

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• 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?

No response

If applicable, what version of Node.js are you using?

No response

Amplify CLI Version

5.5.0

What operating system are you using?

Windows (amplify cli on WSL)

Amplify Categories

api

Amplify Commands

push

Describe the bug

Amplify CLI will sometimes get stuck after multiple amplify push runs to upload each one @key addition to the graphQL schema.

It gets stuck in this step: I’ve waited up to an hour but nothing happens.

Each time this happens I need to terminate the execution, run amplify run to overwrite the changes, apply the changes again and run amplify push again.

Expected behavior

The command should run correctly or time-out automatically and return an error message.

Reproduction steps

1. Add a @key to a current model of your schema.
2. run amplify push
3. Repeat until one of the pushes gets stuck.

GraphQL schema(s)

# Put schemas below this line
# example
type Budgets @model @auth(rules: [{allow: private}])
@key(name: "budgetsBySpacePID", fields: ["spacePID", "ownerPID"], queryField: "budgetsBySpacePID"){
  id: ID!
  pid: ID
  spacePID: ID!
  teamPID: ID
  ownerPID: ID!
  allowedUsersPID: [ID]
  startDate: AWSDate!
  endDate: AWSDate
  fatherBudgetPID: ID
  budgetLevel: Int
  name: String!
  companyID: String
  description: String
  initialAmount: Float!
  usedAmount: Float
  currency: String
}

Log output

# Put your logs below this line
# Log is too long, reaching GitHubs character limit for new issues
# will provide in comment / pm

Additional information

@voltron (aws amplify discord server) mentioned that it could be related to the following error Throttling: Rate exceeded but it does not appear in the logs for the failed execution