This issue is evident with there are about 30 graphql schema. From Amplify CLI version 4.22 going forward, this issue has been consistent and causing issues. It hangs for a while on the cursor in command line and return a Amplify Push Timeout Error. This issue does not exist in 4.21.3.

Attached is a list of 25 graphql schemas that might help replicate the issue using CLI version 4.22 and over.
Hi @KayIlory, The issue exists when a timeout is received when attempting to write to S3 we are working on a fix to retry after a timeout has been received
@ammarkarachi thanks for acknowledging the bug, any update on when we will get a fix for this.
@ammarkarachi thanks for acknowledging the bug, any update on when we will get a fix for this.
and in what version the fix will be present so that I can test as well.
@KayIlory This should be fixed now in the latest version can you try it out?