aws-amplify / aws-amplify/amplify-studio
creating a new record when the data manger is stuck in syncing to cloud state causes unexpected behaviour
- Dominant language
- No language data
- Stars
- 135
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-adminui/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-adminui/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
d3agmbof1zzckq
### Region
us-east-1
### Environment name
dev
### Figma File Version (if applicable)
_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?
_No response_
### Browser type?
_No response_
### Describe the bug
following issue: https://github.com/aws-amplify/amplify-studio/issues/939
once we are in the following state, where the data never fully syncs.
creating a record with all the field as follows
will cause a successful sync
but when refreshing the page the previously failed disappear
### Expected behavior
provided correct status when syncing
### Reproduction steps
1. use the data model provided in https://github.com/aws-amplify/amplify-studio/issues/939
2. create record that causes a failure and shows syncing state
3. create a new record with all fields filled in
4. see that on a refresh the data disappears
### Project Identifier
_No response_
### Additional information
_No response_
Contributor guide
Research direction
Start with the related issue 939 and reproduce the data manager flow described in the reproduction steps: leave one record stuck in syncing, create another complete record, and refresh. Done means the records remain correctly represented and the UI reports the correct syncing status after refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100