Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Bug Report: Jovu create duplicate entities when one of the entities failed to create #8423

Open
yuval-hazaz opened this issue May 7, 2024 · 1 comment 路 Fixed by #8424
Assignees
Labels
type: bug Something isn't working

Comments

@yuval-hazaz
Copy link
Member

What happened?

use this prompt

Create a new service for employee management, including working hours, locations, managers, employees, functions, and salary

Jovu will create all entities correctly but will fail on the creation of the function entity because the name is reserved.

unexepectadly, Jovu will retry to create all entities again with unique names, and we will end up with most entities created twice

What you expected to happen

Jovu should understand that some entities were created successfully and should only try again for the failed entity (or let the user know that this one failed)

How to reproduce

use this prompt, on an existing project that is already connected to a git repo

Create a new service for employee management, including working hours, locations, managers, employees, functions, and salary

Amplication version

No response

Environment

No response

Are you willing to submit PR?

No response

@yuval-hazaz yuval-hazaz added the type: bug Something isn't working label May 7, 2024
@yuval-hazaz yuval-hazaz self-assigned this May 7, 2024
@yuval-hazaz yuval-hazaz linked a pull request May 7, 2024 that will close this issue
2 tasks
@morhag90
Copy link
Member

morhag90 commented May 9, 2024

Passed QA:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants