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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ON CONFLICT DO UPDATE command cannot affect row a second time while loading WorkflowDefinitions #5033

Closed
raymonddenhaan opened this issue Mar 4, 2024 · 3 comments · Fixed by #5067 or #5074
Assignees
Labels
bug Something isn't working
Milestone

Comments

@raymonddenhaan
Copy link
Contributor

This is a continuation of bug #4982.
Due to changes made to the BulkUpsertAsync method we get a different exception, however the cause seems to be the same.

@raymonddenhaan raymonddenhaan added the bug Something isn't working label Mar 4, 2024
@raymonddenhaan raymonddenhaan added this to the Elsa 3.1 milestone Mar 4, 2024
@raymonddenhaan raymonddenhaan self-assigned this Mar 4, 2024
Copy link

glime-ai bot commented Mar 4, 2024

To provide an accurate response, I would need more information about the specific changes made to the BulkUpsertAsync method and the exact exception message you are encountering now. The context provided does not include details about the new exception or the modifications to the method. Could you please provide the exception details and describe the changes made to the BulkUpsertAsync method?

@raymonddenhaan
Copy link
Contributor Author

The reason we ran into the issue after changing the BulkUpsertMethod in #5005 is because the package does not support shadow properties #5046

@raymonddenhaan
Copy link
Contributor Author

This issue occurs when another version of a workflow definition with the same ID is being loaded.
PR #5067 fixes this by adding multiple checks to ensure data integrity.

sfmskywalker added a commit that referenced this issue Mar 13, 2024
Corrected the parameter token in the error log message to match the expected variable name, ensuring accurate logging when attempting to create duplicate workflows. This helps in diagnosing the root cause of issue #5033 more efficiently.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
1 participant