Admin UI - Content - It is not showing the data to manage. (There was an error loading your data)

[micheldelgallo]

Before opening, please confirm:

• [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

amplify pull --appId dwl79gz8syr8a --envName staging

Region

us-east-2

Environment name

No response

Amplify CLI Version

No response

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

No response

What operating system are you using?

Windows

Browser type?

Google Chrome

Describe the bug

The data is not showing and there are a error message.

Expected behavior

I want to see and manage my data in admin UI. The data exists in DynamoDB.

Reproduction steps

Open "Admin UI" Click in "Content" The data is not showing and there are a error message.

Additional information

No response

[pananapread]

Hello! Could you take a screenshot of your console so we can see what the error message is? (to learn how, see https://developer.chrome.com/docs/devtools/overview/#console)

[micheldelgallo]

Hello! here is the browser log:

[yucomds]

Same issue for me.

[prajwalbv99]

@micheldelgallo @yucomds Could you please refer to this try the steps mentioned here and confirm if your issue still exists.

[micheldelgallo]

@prajwalbv99 Ok. I did the reference for #216 issue. Until now, it is not working and I received the same message "There was an error loading your data". thanks

[aaronksaunders]

Followed instructions, still getting this error.. completely blocked in the middle of my project :-(

[brettlyman]

This is also an issue for me, would love to have it resolved as soon as possible -- else I will be forced to abandon Amplify because I really need a working admin UI.

Not sure whether it's relevant, but it says syncQueriesStarted with 6 models, but then only 5 modelSynced entries show up below that. Perhaps it's failing to sync one of the models? For the previous poster's screenshot, I notice it has 3 models but only 1 modelSynced line.

[jessicadturner]

I have the same issue

[prajwalbv99]

@micheldelgallo @jdt11 @brettlyman @aaronksaunders @yucomds We are looking into this issue.

[brettlyman]

Here's another note: if your connection goes "offline" then the content view shows up! I noticed this when my laptop went to sleep and I brought it back up. Also verified by getting the error above, and then in dev console setting network throttling to "offline" and it immediately showed.

[OskarD]

I have this problem too! :))) Do we get any beta testing perks?

[splax-s]

i have this problem too

[splax-s]

Here's another note: if your connection goes "offline" then the content view shows up! I noticed this when my laptop went to sleep and I brought it back up. Also verified by getting the error above, and then in dev console setting network throttling to "offline" and it immediately showed.

yes it also happened to me

[evan-resonare]

Same issue here.

Edit: it seemed to self correct itself.

If others are still having issues, try to go into the DynamoDB AWS service and check through the tables in the items tab to see if there are any invalid or null items.

[WathikAhmed]

Same! There was an error loading your data.

[AlexeSemenenko]

same, and noticed that error appears after adding many to many relationship to my tables

[cslogan-red]

This can happen when field types on models with a many-to-many relationship change or the many-to-many field itself is renamed or changed from not required to required and there is already existing data in your app's underlying DyanmoDB join table(s). DataStore sync's will begin returning errors, which prevents DataStore from fully initializing, which then prevents the Content page from loading.

As a temporary workaround, if you aren't seeing actual errors in your developer console (most of these screenshots), you can see which model is returning a sync error using the "Network" tab in the Chrome or Firefox developer console. Open the "Network" tab and reload the Content page, after it finishes loading, filter on "graphql", there should be a sync request for each of your models. Look at the response and an error message will be present for at least one of the models. You can then go to the corresponding join table in DynamoDB for your many-to-many relationship that is failing to sync (it will be in that "Network" response) and delete any records in this table with missing values. The join tables require values from each model in order to sync properly.

Refresh the Content page and DataStore sync will begin working again. It's in our backlog to automatically detect and provide a better, automated solution for when this type of behavior occurs.

[AlexeSemenenko]

This can happen when field types on models with a many-to-many relationship change or the many-to-many field itself is renamed or changed from not required to required and there is already existing data in your app's underlying DyanmoDB join table(s). DataStore sync's will begin returning errors, which prevents DataStore from fully initializing, which then prevents the Content page from loading.

As a temporary workaround, if you aren't seeing actual errors in your developer console (most of these screenshots), you can see which model is returning a sync error using the "Network" tab in the Chrome or Firefox developer console. Open the "Network" tab and reload the Content page, after it finishes loading, filter on "graphql", there should be a sync request for each of your models. Look at the response and an error message will be present for at least one of the models. You can then go to the corresponding join table in DynamoDB for your many-to-many relationship that is failing to sync (it will be in that "Network" response) and delete any records in this table with missing values. The join tables require values from each model in order to sync properly.

Refresh the Content page and DataStore sync will begin working again. It's in our backlog to automatically detect and provide a better, automated solution for when this type of behavior occurs.

The bottom line is that I just created tables, there was no data in them. I removed everything and created a new Amplify project with same DynamoDB structure and immediately after creating the tables, the same error appears, and the same output in the console. If look at the network: all 3 tables are loaded correctly without items in them (can be seen in the screenshots).

But besides this, there are 12 more requests that contain this:

Too long for a screenshot, so I'll write in text: {"data":null,"errors":[{"path":null,"locations":[{"line":10,"column":7,"sourceName":null}],"message":"Validation error of type FieldUndefined: Field 'chatroom' in type 'ChatRoomUser' is undefined @ 'syncChatRoomUsers/items/chatroom'"}]}

@cslogan-red may be you have new ideas after my comments?

[cslogan-red]

@AlexeSemenenko your particular schema is still sometimes a problem for DataStore itself, we've seen this with reverse m-m relationships (many to many on both sides of a model) when one model also has a 1-m relationship, like in your example. The sync error preventing DataStore from initializing is also the same type that I explained above. Behind the scenes, many to many relationships create a join table in DynamoDB, in this case ChatRoomUser, and the sync is failing because at least one record exists in that join table without the chatroom side of the join populated. You can make sure either side of your m-m relationship is not required in your schema via Data modeling and then "Save and deploy" if so, otherwise look for a record in that underlying ChatRoomUser DynamoDB join table without one side of the join populated and delete it.

We have this tracked in our backlog as an upcoming release to provide the ability to continue syncing your other models even if one model fails to register properly with DataStore (like in this case), so that you can at least save data in your other models until the sync issue is corrected.

[AlexeSemenenko]

@AlexeSemenenko your particular schema is still sometimes a problem for DataStore itself, we've seen this with reverse m-m relationships (many to many on both sides of a model) when one model also has a 1-m relationship, like in your example. The sync error preventing DataStore from initializing is also the same type that I explained above. Behind the scenes, many to many relationships create a join table in DynamoDB, in this case ChatRoomUser, and the sync is failing because at least one record exists in that join table without the chatroom side of the join populated. You can make sure either side of your m-m relationship is not required in your schema via Data modeling and then "Save and deploy" if so, otherwise look for a record in that underlying ChatRoomUser DynamoDB join table without one side of the join populated and delete it.

We have this tracked in our backlog as an upcoming release to provide the ability to continue syncing your other models even if one model fails to register properly with DataStore (like in this case), so that you can at least save data in your other models until the sync issue is corrected.

Checked not required and redeployed - nothing has changed. In DynamoDB have the following picture:

Or I misunderstood something?

(sorry that the problem is not being solved)

[cslogan-red]

@AlexeSemenenko sorry for the trouble, I was able to repro this behavior with a net-new app using your schema, and this appears to be the same DataStore edge case where a 1-M and M-M exist on the same model, for now removing the M-M relationship and redeploying allows DataStore to sync and the Content page to load. I've raised this up with that team and they are investigating, we'll publish an update here when there's more information.

[alrashedf]

I have the same "There was an error loading your data" issue.

When amplify studio accesses https://amplifybackend.ap-south-1.amazonaws.com/backend/appIDXXXX/job/dev, it returns the below. The strange thing is that I can update my env using amplify CLI with no CloudFormation errors! And the API key in the error Reason: API key not found: da2-tuuu5jzpnvdmzamy3xwhqpwfyi is long changed. Amplify Studio simply doesn't update it of forget it.

I've "Save and Deploy"ed several times now and noting is changing. I've toggled "Enable Amplify Studio" off and on in Amplify Studio settings but it doesn't solve the problem.

Help please. Maintaining Amplify is taking way more than necessary and it is taking time away from developing my app.

{
  "jobs": [
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "e645c5af-83e2-4fc1-ac39-3b6618507b93",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1633594108726",
      "updateTime": "1633594331164"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "23f98972-e9a5-45da-99bd-6a150add9a1a",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1629013979570",
      "updateTime": "1629014207462"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "11dacea9-8bb4-401e-98c6-13b13c97f068",
      "operation": "UpdateBackendAPI",
      "status": "FAILED",
      "createTime": "1631347669285",
      "updateTime": "1631347849440",
      "error": "Command failed with exit code 1: /root/.amplify/bin/amplify push --yes
- Fetching updates to backend environment: dev from the cloud.
✔ Successfully pulled backend environment dev from the cloud.
- Uploading files...
- Updating resources in the cloud. This may take a few minutes...
✖ An error occurred when pushing the resources to the cloud
⚠️ Amplify command hooks are disabled in the current execution environment.
⚠️ See https://docs.amplify.aws/cli/usage/runtime-hooks for more information.

    Current Environment: dev
    
┌──────────┬───────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin   │
├──────────┼───────────────┼───────────┼───────────────────┤
│ Api      │ myprojectApi    │ Update    │ awscloudformation │
└──────────┴───────────────┴───────────┴───────────────────┘

GraphQL schema compiled successfully.

Edit your schema at /tmp/amplify-afd3dd9a-ef3c-4fb7-8bf6-ceedd944e5b7/amplify/backend/api/myprojectApi/schema.graphql or place .graphql files in a directory at /tmp/amplify-afd3dd9a-ef3c-4fb7-8bf6-ceedd944e5b7/amplify/backend/api/myprojectApi/schema

UPDATE_IN_PROGRESS amplify-myproject-dev-90054 AWS::CloudFormation::Stack Sat Sep 11 2021 08:08:14 GMT+0000 (Coordinated Universal Time) User Initiated
UPDATE_IN_PROGRESS apimyprojectApi             AWS::CloudFormation::Stack Sat Sep 11 2021 08:08:17 GMT+0000 (Coordinated Universal Time)               

UPDATE_IN_PROGRESS amplify-myproject-dev-90054-apimyprojectApi-19GXRU90BLDI8 AWS::CloudFormation::Stack Sat Sep 11 2021 08:08:18 GMT+0000 (Coordinated Universal Time) User Initiated

UPDATE_IN_PROGRESS GraphQLAPI AWS::AppSync::GraphQLApi Sat Sep 11 2021 08:08:22 GMT+0000 (Coordinated Universal Time) 
UPDATE_COMPLETE    GraphQLAPI AWS::AppSync::GraphQLApi Sat Sep 11 2021 08:08:24 GMT+0000 (Coordinated Universal Time) 

UPDATE_IN_PROGRESS GraphQLSchema AWS::AppSync::GraphQLSchema Sat Sep 11 2021 08:08:26 GMT+0000 (Coordinated Universal Time)                                                                                                                                                                                        
UPDATE_IN_PROGRESS GraphQLAPIKey AWS::AppSync::ApiKey        Sat Sep 11 2021 08:08:26 GMT+0000 (Coordinated Universal Time)                                                                                                                                                                                        
UPDATE_FAILED      GraphQLAPIKey AWS::AppSync::ApiKey        Sat Sep 11 2021 08:08:27 GMT+0000 (Coordinated Universal Time) API key not found: da2-tuuu5jzpnvdmzamy3xwhqpwfyi (Service: AWSAppSync; Status Code: 404; Error Code: NotFoundException; Request ID: 58ae62e5-4913-4df5-a298-63104df4d464; Proxy: null)
UPDATE_FAILED      GraphQLSchema AWS::AppSync::GraphQLSchema Sat Sep 11 2021 08:08:28 GMT+0000 (Coordinated Universal Time) Resource update cancelled                                                                                                                                                              

UPDATE_ROLLBACK_IN_PROGRESS amplify-myproject-dev-90054-apimyprojectApi-19GXRU90BLDI8 AWS::CloudFormation::Stack Sat Sep 11 2021 08:08:29 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [GraphQLAPIKey, GraphQLSchema].

UPDATE_FAILED               apimyprojectApi             AWS::CloudFormation::Stack Sat Sep 11 2021 08:08:39 GMT+0000 (Coordinated Universal Time) Embedded stack arn:aws:cloudformation:ap-south-1:850873171446:stack/amplify-myproject-dev-90054-apimyprojectApi-19GXRU90BLDI8/fc56a230-df17-11eb-8c24-0a75f3903f24 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [GraphQLAPIKey, GraphQLSchema].
UPDATE_ROLLBACK_IN_PROGRESS amplify-myproject-dev-90054 AWS::CloudFormation::Stack Sat Sep 11 2021 08:08:40 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [apimyprojectApi].                                                                                                                                                                                                                                                                  
UPDATE_IN_PROGRESS          apimyprojectApi             AWS::CloudFormation::Stack Sat Sep 11 2021 08:08:43 GMT+0000 (Coordinated Universal Time)                                                                                                                                                                                                                                                                                                                               

UPDATE_IN_PROGRESS GraphQLAPI    AWS::AppSync::GraphQLApi    Sat Sep 11 2021 08:09:06 GMT+0000 (Coordinated Universal Time) 
UPDATE_COMPLETE    GraphQLAPI    AWS::AppSync::GraphQLApi    Sat Sep 11 2021 08:09:07 GMT+0000 (Coordinated Universal Time) 
UPDATE_IN_PROGRESS GraphQLSchema AWS::AppSync::GraphQLSchema Sat Sep 11 2021 08:09:08 GMT+0000 (Coordinated Universal Time) 
UPDATE_COMPLETE    GraphQLAPIKey AWS::AppSync::ApiKey        Sat Sep 11 2021 08:09:08 GMT+0000 (Coordinated Universal Time) 

UPDATE_COMPLETE                              GraphQLSchema                                         AWS::AppSync::GraphQLSchema Sat Sep 11 2021 08:10:10 GMT+0000 (Coordinated Universal Time) 
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS amplify-myproject-dev-90054-apimyprojectApi-19GXRU90BLDI8 AWS::CloudFormation::Stack  Sat Sep 11 2021 08:10:13 GMT+0000 (Coordinated Universal Time) 

UPDATE_COMPLETE                              apimyprojectApi             AWS::CloudFormation::Stack Sat Sep 11 2021 08:10:18 GMT+0000 (Coordinated Universal Time) 
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS amplify-myproject-dev-90054 AWS::CloudFormation::Stack Sat Sep 11 2021 08:10:18 GMT+0000 (Coordinated Universal Time) 

UPDATE_COMPLETE          apimyprojectApi             AWS::CloudFormation::Stack Sat Sep 11 2021 08:10:30 GMT+0000 (Coordinated Universal Time) 
UPDATE_ROLLBACK_COMPLETE amplify-myproject-dev-90054 AWS::CloudFormation::Stack Sat Sep 11 2021 08:10:30 GMT+0000 (Coordinated Universal Time) 

Following resources failed

Resource Name: ulzeorb245hy7bfmcyvifuyvwiGraphQLSchema (AWS::AppSync::GraphQLSchema)
Event Type: update
Reason: Resource update cancelled
URL: https://console.aws.amazon.com/cloudformation/home?region=ap-south-1#/stacks/arn%3Aaws%3Acloudformation%3Aap-south-1%3A850873171446%3Astack%2Famplify-myproject-dev-90054-apimyprojectApi-19GXRU90BLDI8%2Ffc56a230-df17-11eb-8c24-0a75f3903f24/events

Resource Name: arn:aws:appsync:ap-south-1:850873171446:apis/ulzeorb245hy7bfmcyvifuyvwi/apikeys/da2-tuuu5jzpnvdmzamy3xwhqpwfyi (AWS::AppSync::ApiKey)
Event Type: update
Reason: API key not found: da2-tuuu5jzpnvdmzamy3xwhqpwfyi (Service: AWSAppSync; Status Code: 404; Error Code: NotFoundException; Request ID: 58ae62e5-4913-4df5-a298-63104df4d464; Proxy: null)
URL: https://console.aws.amazon.com/cloudformation/home?region=ap-south-1#/stacks/arn%3Aaws%3Acloudformation%3Aap-south-1%3A850873171446%3Astack%2Famplify-myproject-dev-90054-apimyprojectApi-19GXRU90BLDI8%2Ffc56a230-df17-11eb-8c24-0a75f3903f24/events


Resource is not in the state stackUpdateComplete
An error occurred during the push operation: Resource is not in the state stackUpdateComplete"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "c8461de3-dc1f-4428-be90-513314027470",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1638551878021",
      "updateTime": "1638552150543"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "3f175406-b320-429d-860b-03cd676d6761",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1633670964290",
      "updateTime": "1633671127100"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "ca1d162f-fccf-4ced-85c3-1506a61f353c",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1626255427566",
      "updateTime": "1626255670764"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "f657d446-978f-4528-bf6f-dca554079eb2",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631360546114",
      "updateTime": "1631360810858"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "f761e73e-497b-45e1-9982-57ee9a09cdd9",
      "operation": "DeleteBackendAuth",
      "status": "FAILED",
      "createTime": "1631693398495",
      "updateTime": "1631693429673",
      "error": "Command failed with exit code 1: /root/.amplify/bin/amplify push --yes
- Fetching updates to backend environment: dev from the cloud.
✔ Successfully pulled backend environment dev from the cloud.
- Updating resources in the cloud. This may take a few minutes...
✖ An error occurred when pushing the resources to the cloud
⚠️ Amplify command hooks are disabled in the current execution environment.
⚠️ See https://docs.amplify.aws/cli/usage/command-hooks/ for more information.

    Current Environment: dev
    
┌──────────┬─────────────────┬───────────┬───────────────────┐
│ Category │ Resource name   │ Operation │ Provider plugin   │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Auth     │ myproject6a7ffc87 │ Delete    │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Api      │ myprojectApi      │ No Change │ awscloudformation │
└──────────┴─────────────────┴───────────┴───────────────────┘

Template error: instance of Fn::GetAtt references undefined resource authmyproject6a7ffc87
An error occurred during the push operation: Template error: instance of Fn::GetAtt references undefined resource authmyproject6a7ffc87"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "facddcb9-0223-4e06-8298-5d2acd042d84",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631689956275",
      "updateTime": "1631690195117"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "20d35df8-07fd-4328-9649-660e6ba2f919",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631865595282",
      "updateTime": "1631865884479"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "af862b2f-bb79-4513-b4ea-37a995964ad8",
      "operation": "CreateBackendAuth",
      "status": "FAILED",
      "createTime": "1631304774078",
      "updateTime": "1631304804073",
      "error": "Command failed with exit code 1: /root/.amplify/bin/amplify push --yes
- Fetching updates to backend environment: dev from the cloud.
✔ Successfully pulled backend environment dev from the cloud.
- Updating resources in the cloud. This may take a few minutes...
✖ An error occurred when pushing the resources to the cloud
⚠️ Amplify command hooks are disabled in the current execution environment.
⚠️ See https://docs.amplify.aws/cli/usage/runtime-hooks for more information.

    Current Environment: dev
    
┌──────────┬───────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin   │
├──────────┼───────────────┼───────────┼───────────────────┤
│ Auth     │ myproject       │ Create    │ awscloudformation │
├──────────┼───────────────┼───────────┼───────────────────┤
│ Api      │ myprojectApi    │ No Change │ awscloudformation │
└──────────┴───────────────┴───────────┴───────────────────┘

Template error: instance of Fn::GetAtt references undefined resource authmyproject874c20ea
An error occurred during the push operation: Template error: instance of Fn::GetAtt references undefined resource authmyproject874c20ea"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "3494234b-72f2-4216-9a48-d72fd4e3d4c5",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631439144748",
      "updateTime": "1631439434004"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "e508496a-c47f-4217-9db0-5913de69b299",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1638559464813",
      "updateTime": "1638559738598"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "8484bd4d-a350-4cc0-9e74-8098b0de93e5",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631443440189",
      "updateTime": "1631443675714"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "ccaa05e7-94ac-4c20-8454-28377a7a93a8",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1633677728321",
      "updateTime": "1633677982197"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "e09f143f-da4a-4164-97d7-f08f9d665d2a",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1625726164659",
      "updateTime": "1625726426716"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "f7f88802-f4d6-4d56-b72d-38306d3f2838",
      "operation": "DeleteBackendAuth",
      "status": "FAILED",
      "createTime": "1631691051209",
      "updateTime": "1631691080529",
      "error": "Command failed with exit code 1: /root/.amplify/bin/amplify push --yes
- Fetching updates to backend environment: dev from the cloud.
✔ Successfully pulled backend environment dev from the cloud.
- Updating resources in the cloud. This may take a few minutes...
✖ An error occurred when pushing the resources to the cloud
⚠️ Amplify command hooks are disabled in the current execution environment.
⚠️ See https://docs.amplify.aws/cli/usage/command-hooks/ for more information.

    Current Environment: dev
    
┌──────────┬─────────────────┬───────────┬───────────────────┐
│ Category │ Resource name   │ Operation │ Provider plugin   │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Auth     │ myproject6a7ffc87 │ Delete    │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Api      │ myprojectApi      │ No Change │ awscloudformation │
└──────────┴─────────────────┴───────────┴───────────────────┘

Template error: instance of Fn::GetAtt references undefined resource authmyproject6a7ffc87
An error occurred during the push operation: Template error: instance of Fn::GetAtt references undefined resource authmyproject6a7ffc87"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "bd98d334-d6d3-494a-8158-e28facd8e375",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1630562858286",
      "updateTime": "1630563085147"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "47034e85-f52a-416d-8dfd-2660656b0e9e",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1633678662265",
      "updateTime": "1633678913867"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "03465af3-ee17-4d15-87d8-753063d504c7",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1633679226163",
      "updateTime": "1633679460326"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "43269b29-7965-48ad-b178-3a259e3e474b",
      "operation": "GenerateBackendAPIModels",
      "status": "COMPLETED",
      "createTime": "1633677228498",
      "updateTime": "1633677248440"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "12bfa01b-141d-4b63-85c4-58d8df6158c9",
      "operation": "ImportBackendAuth",
      "status": "FAILED",
      "createTime": "1631349300488",
      "updateTime": "1631349324215",
      "error": "Command failed with exit code 1: /root/.amplify/bin/amplify import auth --headless
⚠️ Amplify command hooks are disabled in the current execution environment.
⚠️ See https://docs.amplify.aws/cli/usage/runtime-hooks for more information.
The selected Cognito User Pool does not have at least 1 Web app client configured. Web app clients are app clients without a client secret.
Error: The selected Cognito User Pool does not have at least 1 Web app client configured. Web app clients are app clients without a client secret.
    at headlessImport (/snapshot/node_modules/amplify-category-auth/lib/provider-utils/awscloudformation/import/index.js:789:15)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at Object.executeAmplifyHeadlessCommand (/snapshot/node_modules/amplify-category-auth/lib/index.js:327:13)
    at executePluginModuleCommand (/snapshot/node_modules/@aws-amplify/cli/lib/execution-manager.js:164:5)
    at Object.executeCommand (/snapshot/node_modules/@aws-amplify/cli/lib/execution-manager.js:35:9)
    at Object.run (/snapshot/node_modules/@aws-amplify/cli/lib/index.js:162:9)"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "e8cc666b-f21d-45f4-b0ba-fefb400958ea",
      "operation": "GenerateBackendAPIModels",
      "status": "COMPLETED",
      "createTime": "1631780191616",
      "updateTime": "1631780217878"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "7ab1b134-6a15-403d-9de9-ef11d6ff3b41",
      "operation": "GenerateBackendAPIModels",
      "status": "COMPLETED",
      "createTime": "1629006180823",
      "updateTime": "1629006205464"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "eedeb14e-a311-47c4-9989-a3a52768d624",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1626159262923",
      "updateTime": "1626159500014"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "fc74de91-76cd-4dea-83aa-b1807a699514",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1630580442117",
      "updateTime": "1630580673622"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "ed45b7a9-ff02-46bb-a029-45f036c448ab",
      "operation": "GenerateBackendAPIModels",
      "status": "COMPLETED",
      "createTime": "1631778733820",
      "updateTime": "1631778745812"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "353bc14c-7667-4a08-a8aa-2e00b54bf66c",
      "operation": "UpdateBackendAPI",
      "status": "FAILED",
      "createTime": "1625658739657",
      "updateTime": "1625658771935",
      "error": "Command failed with exit code 1: /root/.amplify/bin/amplify push --yes
- Fetching updates to backend environment: dev from the cloud.
✔ Successfully pulled backend environment dev from the cloud.
- Uploading files...
- Updating resources in the cloud. This may take a few minutes...
✖ An error occurred when pushing the resources to the cloud

Current Environment: dev

| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Api      | myprojectApi    | Update    | awscloudformation |
| Auth     | myprojectAuth   | No Change | awscloudformation |

GraphQL schema compiled successfully.

Edit your schema at /tmp/amplify-bfa8d8f4-afaf-4414-aee8-7b46005327b7/amplify/backend/api/myprojectApi/schema.graphql or place .graphql files in a directory at /tmp/amplify-bfa8d8f4-afaf-4414-aee8-7b46005327b7/amplify/backend/api/myprojectApi/schema

Template error: instance of Fn::GetAtt references undefined resource authmyproject_userpool_1
An error occurred during the push operation: Template error: instance of Fn::GetAtt references undefined resource authmyproject_userpool_1"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "135b3a81-d9de-4ae3-8aee-e3f896f6da57",
      "operation": "DeleteBackendAuth",
      "status": "COMPLETED",
      "createTime": "1631349989437",
      "updateTime": "1631350023339"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "2151a644-9e44-444b-9459-80c986c439a2",
      "operation": "GenerateBackendAPIModels",
      "status": "COMPLETED",
      "createTime": "1638559338971",
      "updateTime": "1638559384662"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "c4a052cd-e3d8-4fdb-a94d-5ffd1daaa2ce",
      "operation": "GenerateBackendAPIModels",
      "status": "COMPLETED",
      "createTime": "1631359038150",
      "updateTime": "1631359062815"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "963a4c8d-9239-42d6-b9e2-6cd9d46007e3",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631609362517",
      "updateTime": "1631609565582"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "933ae83b-f190-4675-9ebf-34af49f993ba",
      "operation": "GenerateBackendAPIModels",
      "status": "COMPLETED",
      "createTime": "1631777345361",
      "updateTime": "1631777374578"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "7fcd33b4-550e-4504-92da-a05dc4a9c95a",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1630956149198",
      "updateTime": "1630956383728"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "e303cb25-a3d6-4011-a9a7-5b3d458b2fe3",
      "operation": "UpdateBackendAPI",
      "status": "FAILED",
      "createTime": "1625660080638",
      "updateTime": "1625660105052",
      "error": "Command failed with exit code 1: /root/.amplify/bin/amplify push --yes
- Fetching updates to backend environment: dev from the cloud.
✔ Successfully pulled backend environment dev from the cloud.
- Uploading files...
- Updating resources in the cloud. This may take a few minutes...
✖ An error occurred when pushing the resources to the cloud

Current Environment: dev

| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Api      | myprojectApi    | Update    | awscloudformation |
| Auth     | myprojectAuth   | No Change | awscloudformation |

GraphQL schema compiled successfully.

Edit your schema at /tmp/amplify-61f5bfe0-690b-459f-9bf8-1d275df2aa41/amplify/backend/api/myprojectApi/schema.graphql or place .graphql files in a directory at /tmp/amplify-61f5bfe0-690b-459f-9bf8-1d275df2aa41/amplify/backend/api/myprojectApi/schema

Template error: instance of Fn::GetAtt references undefined resource authmyproject_userpool_1
An error occurred during the push operation: Template error: instance of Fn::GetAtt references undefined resource authmyproject_userpool_1"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "23361b72-b546-488f-8e15-3fc44bcf2def",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1638555599376",
      "updateTime": "1638555849765"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "adaff98f-12d5-416f-8134-3afe1959af7f",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631692349947",
      "updateTime": "1631692585515"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "25da2f71-8b5b-4247-8d11-f044bda6ba01",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631000937979",
      "updateTime": "1631001185047"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "b367a8a1-3a42-4fed-9169-1e521e947ed9",
      "operation": "CreateBackendAuth",
      "status": "FAILED",
      "createTime": "1631340755287",
      "updateTime": "1631340785948",
      "error": "Command failed with exit code 1: /root/.amplify/bin/amplify push --yes
- Fetching updates to backend environment: dev from the cloud.
✔ Successfully pulled backend environment dev from the cloud.
- Updating resources in the cloud. This may take a few minutes...
✖ An error occurred when pushing the resources to the cloud
⚠️ Amplify command hooks are disabled in the current execution environment.
⚠️ See https://docs.amplify.aws/cli/usage/runtime-hooks for more information.

    Current Environment: dev
    
┌──────────┬───────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin   │
├──────────┼───────────────┼───────────┼───────────────────┤
│ Auth     │ myproject       │ Create    │ awscloudformation │
├──────────┼───────────────┼───────────┼───────────────────┤
│ Api      │ myprojectApi    │ No Change │ awscloudformation │
└──────────┴───────────────┴───────────┴───────────────────┘

Template error: instance of Fn::GetAtt references undefined resource authmyproject874c20ea
An error occurred during the push operation: Template error: instance of Fn::GetAtt references undefined resource authmyproject874c20ea"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "7c38c298-914b-487b-8a8e-fa93b2967d92",
      "operation": "UpdateBackendAPI",
      "status": "FAILED",
      "createTime": "1625670294153",
      "updateTime": "1625670327263",
      "error": "Command failed with exit code 1: /root/.amplify/bin/amplify push --yes
- Fetching updates to backend environment: dev from the cloud.
✔ Successfully pulled backend environment dev from the cloud.
- Uploading files...
- Updating resources in the cloud. This may take a few minutes...
✖ An error occurred when pushing the resources to the cloud

Current Environment: dev

| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Api      | myprojectApi    | Update    | awscloudformation |
| Auth     | myprojectAuth   | No Change | awscloudformation |

GraphQL schema compiled successfully.

Edit your schema at /tmp/amplify-2cc1087a-3f82-4ddb-8c53-1dd12bf06b72/amplify/backend/api/myprojectApi/schema.graphql or place .graphql files in a directory at /tmp/amplify-2cc1087a-3f82-4ddb-8c53-1dd12bf06b72/amplify/backend/api/myprojectApi/schema

Template error: instance of Fn::GetAtt references undefined resource authmyproject_userpool_1
An error occurred during the push operation: Template error: instance of Fn::GetAtt references undefined resource authmyproject_userpool_1"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "fd65af1b-8562-4636-a882-1d3996d6d4f5",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1630563571502",
      "updateTime": "1630563798045"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "b69d845f-1f45-4813-b128-269239380b48",
      "operation": "GenerateBackendAPIModels",
      "status": "COMPLETED",
      "createTime": "1631606311811",
      "updateTime": "1631606329288"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "118eb428-5878-4869-b8f1-2302d2e0f5a0",
      "operation": "ImportBackendAuth",
      "status": "COMPLETED",
      "createTime": "1631349462865",
      "updateTime": "1631349495793"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "41e0e6fe-3d49-4805-a9fa-91db30ad4c11",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631358456245",
      "updateTime": "1631358688523"
    },
    {
      "appId": "appIDXXXX",
      "backendEnvironmentName": "dev",
      "jobId": "142878ae-e500-4921-be0d-0526a83366e2",
      "operation": "UpdateBackendAPI",
      "status": "COMPLETED",
      "createTime": "1631029763682",
      "updateTime": "1631029991890"
    }
  ],
  "appId": "appIDXXXX",
  "backendEnvironmentName": "dev"
}

[alrashedf]

So, when I opened the laptop the next day, the error "There was an error loading your data." disappeared and I see my "Content"! I don't know what happened. But this is the console log for the Amplify team to decipher. It includes logs before and after I closed my laptop.

[Log] i18next: languageChanged – "en-US" (544.8d441734.chunk.js, line 2)
[Log] i18next: initialized – Object (544.8d441734.chunk.js, line 2)
Object
[Warning] i18next::translator: key "inputError.empty" for languages "en-US, en" won't get resolved as namespace "schemaDesign" was not yet loaded – "This means something IS WRONG in your setup. You access the t function before i18next.init / i18next.loadNamespace / i18next.changeLanguag…" (544.8d441734.chunk.js, line 2)
"This means something IS WRONG in your setup. You access the t function before i18next.init / i18next.loadNamespace / i18next.changeLanguage was done. Wait for the callback or Promise to resolve before accessing it!!!"
[Warning] i18next::translator: key "manageContent.tableActionOptions.delete" for languages "en-US, en" won't get resolved as namespace "translation" was not yet loaded – "This means something IS WRONG in your setup. You access the t function before i18next.init / i18next.loadNamespace / i18next.changeLanguag…" (544.8d441734.chunk.js, line 2)
"This means something IS WRONG in your setup. You access the t function before i18next.init / i18next.loadNamespace / i18next.changeLanguage was done. Wait for the callback or Promise to resolve before accessing it!!!"
[Warning] i18next::translator: key "footer.partOne" for languages "en-US, en" won't get resolved as namespace "appHeader" was not yet loaded – "This means something IS WRONG in your setup. You access the t function before i18next.init / i18next.loadNamespace / i18next.changeLanguag…" (544.8d441734.chunk.js, line 2)
"This means something IS WRONG in your setup. You access the t function before i18next.init / i18next.loadNamespace / i18next.changeLanguage was done. Wait for the callback or Promise to resolve before accessing it!!!"
[Error] Did not parse stylesheet at 'https://ap-south-1.admin.amplifyapp.com/admin/d14jbnnuz8mpdk/dev/~react-simple-tree-menu/dist/main.css' because non CSS MIME types are not allowed in strict mode.
[Log] GQL Transformer Version: 1 (main.e8fd9b60.chunk.js, line 1)
[Error] [Report Only] Refused to connect to https://raw.githubusercontent.com/aws-amplify/amplify-adminui/main/markdown/tests/flutter/flutter_step5.md because it does not appear in the connect-src directive of the Content Security Policy.
[Warning] [AwsUi]  – "[awsui-select]" – "The `selectedId` property has been deprecated. Use `selectedOption` instead." (544.8d441734.chunk.js, line 2)
[Error] [Report Only] Refused to connect to https://raw.githubusercontent.com/aws-amplify/amplify-adminui/main/markdown/tests/flutter/flutter_step5_data_code.md because it does not appear in the connect-src directive of the Content Security Policy.
[Log] starting list jobs poller... (main.e8fd9b60.chunk.js, line 1)
[Error] [Report Only] Refused to connect to https://raw.githubusercontent.com/aws-amplify/amplify-adminui/main/markdown/tests/flutter/flutter_step5.md because it does not appear in the connect-src directive of the Content Security Policy.
[Error] [Report Only] Refused to connect to https://raw.githubusercontent.com/aws-amplify/amplify-adminui/main/markdown/tests/flutter/flutter_step5_data_code.md because it does not appear in the connect-src directive of the Content Security Policy.
[Log] Object (main.e8fd9b60.chunk.js, line 1)
[Warning] The schema has already been initialized (544.8d441734.chunk.js, line 2)
[Log] appsync – "storageSubscribed" – undefined (main.e8fd9b60.chunk.js, line 1)
[Log] appsync – "networkStatus" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Log] appsync – "subscriptionsEstablished" – undefined (main.e8fd9b60.chunk.js, line 1)
[Log] appsync – "outboxStatus" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Log] appsync – "syncQueriesStarted" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Log] appsync – "modelSynced" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Log] appsync – "modelSynced" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Log] appsync – "modelSynced" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Error] Unhandled Promise Rejection: Error: Field details should be of type object, boolean received. true
    (anonymous function) (544.8d441734.chunk.js:2:4676047)
    s (544.8d441734.chunk.js:2:4674874)
    promiseReactionJob
[Error] [Report Only] Refused to connect to https://0loq6ibbwc.execute-api.ap-south-2.amazonaws.com/prod/v1/log because it does not appear in the connect-src directive of the Content Security Policy.
[Error] [Report Only] Refused to connect to https://0loq6ibbwc.execute-api.ap-south-2.amazonaws.com/prod/v1/log because it does not appear in the connect-src directive of the Content Security Policy.
[Error] Beacon API cannot load https://0loq6ibbwc.execute-api.ap-south-2.amazonaws.com/prod/v1/log. A server with the specified hostname could not be found.
[Error] Failed to load resource: A server with the specified hostname could not be found. (log, line 0)
[Error] [Report Only] Refused to connect to https://unagi-na.amazon.com/1/events/com.amazon.eel.katal.metrics.core.nexus because it does not appear in the connect-src directive of the Content Security Policy.
[Error] [Report Only] Refused to connect to https://unagi-na.amazon.com/1/events/com.amazon.eel.katal.metrics.core.nexus because it does not appear in the connect-src directive of the Content Security Policy.
[Error] [Report Only] Refused to connect to https://0loq6ibbwc.execute-api.ap-south-2.amazonaws.com/prod/v1/log because it does not appear in the connect-src directive of the Content Security Policy.
[Error] [Report Only] Refused to connect to https://0loq6ibbwc.execute-api.ap-south-2.amazonaws.com/prod/v1/log because it does not appear in the connect-src directive of the Content Security Policy.
[Error] Beacon API cannot load https://0loq6ibbwc.execute-api.ap-south-2.amazonaws.com/prod/v1/log. A server with the specified hostname could not be found.
[Error] Failed to load resource: A server with the specified hostname could not be found. (log, line 0)
[Error] [Report Only] Refused to connect to https://unagi-na.amazon.com/1/events/com.amazon.eel.katal.metrics.core.nexus because it does not appear in the connect-src directive of the Content Security Policy.
[Error] [Report Only] Refused to connect to https://unagi-na.amazon.com/1/events/com.amazon.eel.katal.metrics.core.nexus because it does not appear in the connect-src directive of the Content Security Policy.
[Error] The Internet connection appears to be offline.
[Error] Fetch API cannot load https://cognito-idp.ap-south-1.amazonaws.com/ due to access control checks.
[Error] Failed to load resource: The Internet connection appears to be offline. (cognito-idp.ap-south-1.amazonaws.com, line 0)
[Error] The Internet connection appears to be offline.
[Error] Fetch API cannot load https://cognito-identity.ap-south-1.amazonaws.com/ due to access control checks.
[Error] Failed to load resource: The Internet connection appears to be offline. (cognito-identity.ap-south-1.amazonaws.com, line 0)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Log] appsync – "networkStatus" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Log] appsync – "ready" – undefined (main.e8fd9b60.chunk.js, line 1)
[Warning] [AwsUi]  – "[awsui-select]" – "The `selectedId` property has been deprecated. Use `selectedOption` instead." (544.8d441734.chunk.js, line 2)
[Warning] [AwsUi]  – "Region alias \"text\" for \"Button\" has been deprecated. Use \"children\" prop instead" (544.8d441734.chunk.js, line 2)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] WebSocket connection to 'wss://ecqqs7odrfe7xmrkdkrjbrn4eu.appsync-realtime-api.ap-south-1.amazonaws.com/graphql?header=eyJhY2NlcHQiOiJhcHBsaWNhdGlvbi9qc29uLCB0ZXh0L2phdmFzY3JpcHQiLCJjb250ZW50LWVuY29kaW5nIjoiYW16LTEuMCIsImNvbnRlbnQtdHlwZSI6ImFwcGxpY2F0aW9uL2pzb247IGNoYXJzZXQ9VVRGLTgiLCJob3N0IjoiZWNxcXM3b2RyZmU3eG1ya2Rrcmpicm40ZXUuYXBwc3luYy1hcGkuYXAtc291dGgtMS5hbWF6b25hd3MuY29tIiwieC1hbXotZGF0ZSI6IjIwMjExMjA0VDIwNTI1N1oiLCJYLUFtei1TZWN1cml0eS1Ub2tlbiI6IklRb0piM0pwWjJsdVgyVmpFSTMvLy8vLy8vLy8vd0VhQ21Gd0xYTnZkWFJvTFRFaVNEQkdBaUVBNUVWcDNOaFZkbFNMRnlrRmpoM24vVUR4VGMzMnFTVHJXM2JWOUZObDdna0NJUUN6eG5ZZUpwM3ErVGtISVJSTDFUYkFXL1lEOWs0Q3dOQlEwREYzRWNIalp5cktCQWhtRUFBYUREZzFNRGczTXpFM01UUTBOaUlNRndCSkdxdHZ0NnRSekR5L0txY0Uwbi9TUy9DMXdUSVNtUDUyNmI3MlVXTy9UTExySzhCOHNhdnBVdmdpZkFHaldITkFCcVp0a2gvWlNrVGNLM1ZTRUFTRW9pUzlHbWF1eTZuaHZ1U0ZEL0wyOWZjdWdTRGlwZ0k1dzEraVZNS01yU2M0OWY5UWJxOUF2SDUvNE15ZFQ4NWZnZ0VWUzVHdzVaOTZTR3BjRHEwaUdrRnIrZlhJRlFieVJPeWlzRVUxc2RrTW9Wd2hYaGM2Zkk0MVVOZEVRVlg1MXVkbE9RZzU3ZmI3TWpvVk84WWNLM2ZpN2dzRE9HN01zQkpQNzVwTnR5ZVFUL1hoMVZLcXdLZGlDT1NaQm83d29IT0FKdm1UMHEzRGREbkFjbCsvdzhhOU9TUGNWTE1IdG82bThHeTliZ1VKdFJDY1hnNSs3Yy9kZ05VQ0xyNTh0M1FEd0lOZjZ4TUVkdDhJZlEvVEhnRUxKT0VsOGhGeFZzRkZnVkNXZ2MvYzZ1N0ZKTFpLOXNEa2h1NjV5WTZ6ajBleDEyZ3ZMWkltSm5xa1lOb1hWNFptVE5mZzVKMVRyd0lySElMRzlyMHVBR1dLUUkvSm9WeUNhWE5iNllDRWVPUTl0WU9tUVFkckJWb0xTTktwZ0RvRVQ4Zm8zY1YrYlJaME55Y1lYNW1PblNNMkZmUGFEWC9MQzVtdlZScDJxN2dKR0Nud1VuUzhPRThTY3dUTWJoZ0prczdhSndrK3FpaUdQbVFrZ01KdVlPNitHdW1HUkNybDVjWml1M3h3TlJjVHUyVHc3dGExdEhDdlp4TzI2UXJ1alBoTG9XdkxxeDlFZHNDc2hnL0h2YURGa3ZYVVBWMEVRY2FjdVNEYUdwRXo0bDNSTUZ0bjVaVUhJNUg0VXlkZWkwam54b1dKdThqc2g4SzAzSXd4dkJmMTVRMUdjZ0tyREVrMnhaNkx3RXlXWkh2SE9wWEtrVGhXbHhlUHdpRkdmWjh3cUtxdmpRWTZoQUxlaER0WFlxR2dBeHlGeS9pRlpMNFpFcDZpakxiNmxGb1hlNzl1U1N5WjUyUU1uVGwyWGptK09TMUFIMFhCVnp4dHJXR0FYU01leUNuR0MyOWhCckg0OFlpZ0xpYy9FeFRaL1hDU1g0eW9zbC85T0NydXhaM1ZGT2hyQTZxSGEwcGhNbTlkUVRrcnBLTEFGVVdqa2xQb01NNGUrQ0t2d0diejRZbVc0MnZYT3JTTFVaNE5MSEdsT3pTaFBBR1ZOREppSHpPbXBuaVc3NDAwdVRENmdBRXlwTlk2Q05lRS8rTmYzb1FNZ1FDc3NNMzNLUWNUZHBpakFVaXRDV1VmNTQ1UFpFOTExeUdGQnVNUVRzQVg4c1lkWEZSbElMcjQvVTVrUkgzaTVYd0h2dCtqbHNkR1NQaUFJclE2d09LUXZKTWwvcjVGWUxNZmliZ09iVG04S0lrV0dYUGk1Zz09IiwiQXV0aG9yaXphdGlvbiI6IkFXUzQtSE1BQy1TSEEyNTYgQ3JlZGVudGlhbD1BU0lBNE1HNzZIWDNPTkwyQ00zUy8yMDIxMTIwNC9hcC1zb3V0aC0xL2FwcHN5bmMvYXdzNF9yZXF1ZXN0LCBTaWduZWRIZWFkZXJzPWFjY2VwdDtjb250ZW50LWVuY29kaW5nO2NvbnRlbnQtdHlwZTtob3N0O3gtYW16LWRhdGU7eC1hbXotc2VjdXJpdHktdG9rZW4sIFNpZ25hdHVyZT04NDQ1YjJlY2Q3Y2U2MTBkODY3MDY3NDgxMDI3MWQ5MDU4MDc2NzFlOWMwN2QzM2IwMTIyNGRhYjA3NzBjNDE2In0=&payload=e30=' failed: The operation couldn’t be completed. (kNWErrorDomainPOSIX error 60 - Operation timed out)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Log] appsync – "networkStatus" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Log] appsync – "subscriptionsEstablished" – undefined (main.e8fd9b60.chunk.js, line 1)
[Log] appsync – "syncQueriesStarted" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Unhandled Promise Rejection: Error: Field details should be of type object, boolean received. true
    (anonymous function) (544.8d441734.chunk.js:2:4676047)
    s (544.8d441734.chunk.js:2:4674874)
    promiseReactionJob
[Error] [Report Only] Refused to connect to https://0loq6ibbwc.execute-api.ap-south-2.amazonaws.com/prod/v1/log because it does not appear in the connect-src directive of the Content Security Policy.
[Error] [Report Only] Refused to connect to https://0loq6ibbwc.execute-api.ap-south-2.amazonaws.com/prod/v1/log because it does not appear in the connect-src directive of the Content Security Policy.
[Error] Beacon API cannot load https://0loq6ibbwc.execute-api.ap-south-2.amazonaws.com/prod/v1/log. A server with the specified hostname could not be found.
[Error] Failed to load resource: A server with the specified hostname could not be found. (log, line 0)
[Log] appsync – "modelSynced" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Log] appsync – "modelSynced" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Log] appsync – "modelSynced" – Object (main.e8fd9b60.chunk.js, line 1)
Object
[Error] [Report Only] Refused to connect to https://unagi-na.amazon.com/1/events/com.amazon.eel.katal.metrics.core.nexus because it does not appear in the connect-src directive of the Content Security Policy.
[Error] [Report Only] Refused to connect to https://unagi-na.amazon.com/1/events/com.amazon.eel.katal.metrics.core.nexus because it does not appear in the connect-src directive of the Content Security Policy.
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1n — config.js:400(anonymous function) — config.js:421getCredentials — config.js:430(anonymous function) — event_listeners.js:81callListeners — sequential_executor.js:102emit — sequential_executor.js:78emitEvent — request.js:686e — request.js:22(anonymous function) — state_machine.js:14runTo — request.js:406(anonymous function) — request.js:795Promise(anonymous function) — request.js:781c — runtime.js:63(anonymous function) — runtime.js:294n — asyncToGenerator.js:3s — asyncToGenerator.js:25promiseReactionJob
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob
[Log] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 (main.e8fd9b60.chunk.js, line 1)
[Error] Error listing jobs – CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
    (anonymous function) (main.e8fd9b60.chunk.js:1:833486)
    c (544.8d441734.chunk.js:2:8888784)
    (anonymous function) (544.8d441734.chunk.js:2:8888534)
    n (544.8d441734.chunk.js:2:681929)
    u (544.8d441734.chunk.js:2:682169)
    promiseReactionJob

[AlexeSemenenko]

@AlexeSemenenko sorry for the trouble, I was able to repro this behavior with a net-new app using your schema, and this appears to be the same DataStore edge case where a 1-M and M-M exist on the same model, for now removing the M-M relationship and redeploying allows DataStore to sync and the Content page to load. I've raised this up with that team and they are investigating, we'll publish an update here when there's more information.

@cslogan-red thank you too much, will wait here for your message with news

[cslogan-red]

@AlexeSemenenko see the latest comment on #388 for explanation and temporary workaround until this becomes possible.

[gzimbron]

Im getting this in console

[AechDub]

@pptavozl it looks like you have one more error above the info logs there. Can you post with the full error list?

[gzimbron]

@AechDub
Sure! Thanks!

[AechDub]

This appears to potentially be an issue with your schema @pptavozl. Could you also share this? Did you recently add relationships or required fields to your models that were not previously there?

[gzimbron]

@AechDub

I fixed removing a Model. I'll try to redesign

[hisstoryxx]

@cslogan-red I have a same issue as @AlexeSemenenko case

plz figure out the reason and solutions !!!

[MilinkoDragovic]

I have the same error regarding this issue. I was following the tutorials by creating the todo app and I am having a problem with accessing the Content.

[hisstoryxx]

@cslogan-red @AlexeSemenenko @MilinkoDragovic I found a way myself. Just build in schema not using amplify studio data model https://github.com/aws-amplify/amplify-adminui/issues/397#issuecomment-993303445

[johnrusch]

Getting this error as well. Stopped being able to see the Content page after adding items to the table through the DynamoDB sdk in a lambda.

Also got this.

[gzimbron]

Hello, i removed a table from schema.graphql, then i pushed changes all changes applied, but in console i receive this :

Failed to create models in the cloud: Modelgen job creation failed

and then i went to Amplify Studio -> Data and got this:

Model was deleted but few subscriptions did not

[cslogan-red]

This failure can't occur the same way any longer as the error handling behavior has been isolated to each individual model as opposed to blocking the entire CMS, see #474 for tracking on improvements. The DataStore team is currently working on an improved error handling release that will allow us to implement the instrumentation to show you more helpful error messages when various different types of sync errors occur, as well as how to correct them.