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

API-method "append" and duplicate check #284

hugbug opened this issue Sep 17, 2016 · 0 comments


None yet
1 participant
Copy link

commented Sep 17, 2016

When adding nzb-file if duplicate check puts it straight to history with status DUPE, COPY, etc. the API-method "append" returns "-1" as indication of an error.

One consequence of this is that the automation programs may try to send the same file again (and again).

It would be better to return the ID of item in the history instead of "-1". That will allow the other programs check the status of nzb and react properly.

@hugbug hugbug added the improvement label Sep 17, 2016

@hugbug hugbug added this to the v18 milestone Sep 17, 2016

@hugbug hugbug closed this in f28c049 Sep 17, 2016

hugbug added a commit that referenced this issue Oct 9, 2017

fixed #284: API-method "append" and dupe check
method “append” returns nzb-id also for items added straight to history.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.