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

Rethink how sync adapter exposes batch errors / failed records. #18

Closed
thomcc opened this issue May 2, 2018 · 2 comments
Closed

Rethink how sync adapter exposes batch errors / failed records. #18

thomcc opened this issue May 2, 2018 · 2 comments

Comments

@thomcc
Copy link
Contributor

thomcc commented May 2, 2018

At the moment it's largely taken straight from desktop, but this seems error prone and less than ideal.

See #12 (comment) for some more context.

┆Issue is synchronized with this Jira Story

@mhammond
Copy link
Member

I think the tl;dr of this is that posting a batch either works or it doesn't. Allowing some records to fail but have the batch succeed seems too vague to be useful without much tighter semantics (which can be added later if they actually appear in practice)

dmose pushed a commit to dmose/application-services that referenced this issue Mar 15, 2021
@jdragojevic
Copy link
Contributor

Closing - sounds like not something we committed to doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants