Dane Pilcher

This appears to be a bug. `id` should be auto-populated in the `@primaryKey` on `id` field with sort key case. https://docs.amplify.aws/lib/datastore/advanced-workflows/q/platform/js/#determine-when-the-primary-key-field-is-auto-populated-upon-record-creation

Dependent on https://github.com/aws-amplify/amplify-js/pull/11707

Hi @harshit9715, this is intended workflow for overriding when using the construct directly. I'll leave this open as a feature request.

Creating fake resolvers may allow you to get out of the UPDATE_ROLLBACK_FAILED state. https://github.com/aws-amplify/amplify-category-api/issues/2157#issuecomment-1868341419

Are there any additional error messages on the CloudFormation console?

There are a few possible solutions in https://github.com/aws-amplify/amplify-category-api/issues/92.

I wasn't able to reproduce this issue. Are you certain there were no other error messages?

Adding the `TokenAuthorizer` creates a cyclical dependency between the API GW stack and the lambda function stack. You can break the dependency by supplying the auth function ARN to the...

I believe you are on the right track @PlusA2M. The fix for this issue is likely entirely in https://github.com/aws-amplify/amplify-category-api. I'll leave this issue open for visibility.

Thanks for the additional information. We are looking into a fix now.