Mixing
Amazon MWS, feed submission IDs returned are not unique
0
Trying to integrate Amazon MWS into our software.
It would appear that the FeedSubmissionId(s) returned by SubmitFeed() are, at times, not unique. I found out the hard way, as the database returned an error since I have FeedSubmissionId as a Primary Key.
The issue went away since, after a few failed attempts, some time passed and SubmitFeed() finally returned a not-previously-used ID.
Can anyone confirm what I am seeing? FeedSubmissionId(s) not being unique? Is Amazon 'reusing' them? Are we supposed to use them and immediately discard them under the theory that could be 'reused'?
Thanks for your inputs!
amazon-mws
asked Nov 20 '18 at 18:28
sexybitsexybit
13
add a comment |
0
Trying to integrate Amazon MWS into our software.
It would appear that the FeedSubmissionId(s) returned by SubmitFeed() are, at times, not unique. I found out the hard way, as the database returned an error since I have FeedSubmissionId as a Primary Key.
The issue went away since, after a few failed attempts, some time passed and SubmitFeed() finally returned a not-previously-used ID.
Can anyone confirm what I am seeing? FeedSubmissionId(s) not being unique? Is Amazon 'reusing' them? Are we supposed to use them and immediately discard them under the theory that could be 'reused'?
Thanks for your inputs!
amazon-mws
asked Nov 20 '18 at 18:28
sexybitsexybit
13
I guess I don't understand how you are using it. You submit a feed and then store that id so you can later query to get a feed processing status? You should never use that id as the primary key to your table. You can't guarantee uniqueness as you've found.
– ScottG
Dec 8 '18 at 16:02
Hi ScottG, thanks for replying. Indeed, the intended use is the one you described. The documentation does say that the ID is unique. Anyhow, I have a slew of verified cases in which the same id is returned for a new feed e.g. 12h later and, if queried using GetFeedSubmissionList(), you can see that the SubmittedDate still refers to the first submitted feed. I am just trying to figure out how to handle this whole thing. Right now I'm just disregarding them and retrying SubmitFeed() multiple times till I get a new ID. Thanks for your input.
– sexybit
Dec 9 '18 at 19:46
what is the purpose for calling submitfeed multiple times? I submit a feed and then in a loop, I check every xx seconds to see if it was successful or not. If not successful, I have I data problem, more than likely, so I use my notify process to alert me(the admin) that something is wrong. I really could care less about the feed submission id. I just use that to query the status of the submit request. Once the request is submitted successfully, I'll log it, just so I can have an audit trail (my log has it's own PK ID, it's not feedsubmittionid), but then I don't care about it any more.
– ScottG
Dec 10 '18 at 14:53
At first I wasn't sure if the ID was being "reused" or not. Meaning that if I got the same ID for a new feed I was left wondering if it "pointed" to the new feed or the old one. I was calling SubmitFeed() multiple times, i.e. trying to resubmit the new feed, to get an "unambiguous" id. Clearly, I will now adopt my own PK but that won't solve the main issue: the ID pointing to the "old" feed. I can't call GetFeedSubmissionList() or GetFeedSubmissionResult(). I need to disregard the ID, resubmit the feed till I get a brand new ID. MWS Support has been "investigating" this for over a month.
– sexybit
Dec 10 '18 at 16:47
add a comment |
0
0
0
Trying to integrate Amazon MWS into our software.
It would appear that the FeedSubmissionId(s) returned by SubmitFeed() are, at times, not unique. I found out the hard way, as the database returned an error since I have FeedSubmissionId as a Primary Key.
The issue went away since, after a few failed attempts, some time passed and SubmitFeed() finally returned a not-previously-used ID.
Can anyone confirm what I am seeing? FeedSubmissionId(s) not being unique? Is Amazon 'reusing' them? Are we supposed to use them and immediately discard them under the theory that could be 'reused'?
Thanks for your inputs!
amazon-mws
asked Nov 20 '18 at 18:28
sexybitsexybit
13
Trying to integrate Amazon MWS into our software.
It would appear that the FeedSubmissionId(s) returned by SubmitFeed() are, at times, not unique. I found out the hard way, as the database returned an error since I have FeedSubmissionId as a Primary Key.
The issue went away since, after a few failed attempts, some time passed and SubmitFeed() finally returned a not-previously-used ID.
Can anyone confirm what I am seeing? FeedSubmissionId(s) not being unique? Is Amazon 'reusing' them? Are we supposed to use them and immediately discard them under the theory that could be 'reused'?
Thanks for your inputs!
amazon-mws
amazon-mws
asked Nov 20 '18 at 18:28
sexybitsexybit
13
asked Nov 20 '18 at 18:28
sexybitsexybit
13
asked Nov 20 '18 at 18:28
sexybitsexybit
13
asked Nov 20 '18 at 18:28
sexybitsexybit
13
asked Nov 20 '18 at 18:28
sexybitsexybit
13
13
I guess I don't understand how you are using it. You submit a feed and then store that id so you can later query to get a feed processing status? You should never use that id as the primary key to your table. You can't guarantee uniqueness as you've found.
– ScottG
Dec 8 '18 at 16:02
Hi ScottG, thanks for replying. Indeed, the intended use is the one you described. The documentation does say that the ID is unique. Anyhow, I have a slew of verified cases in which the same id is returned for a new feed e.g. 12h later and, if queried using GetFeedSubmissionList(), you can see that the SubmittedDate still refers to the first submitted feed. I am just trying to figure out how to handle this whole thing. Right now I'm just disregarding them and retrying SubmitFeed() multiple times till I get a new ID. Thanks for your input.
– sexybit
Dec 9 '18 at 19:46
what is the purpose for calling submitfeed multiple times? I submit a feed and then in a loop, I check every xx seconds to see if it was successful or not. If not successful, I have I data problem, more than likely, so I use my notify process to alert me(the admin) that something is wrong. I really could care less about the feed submission id. I just use that to query the status of the submit request. Once the request is submitted successfully, I'll log it, just so I can have an audit trail (my log has it's own PK ID, it's not feedsubmittionid), but then I don't care about it any more.
– ScottG
Dec 10 '18 at 14:53
At first I wasn't sure if the ID was being "reused" or not. Meaning that if I got the same ID for a new feed I was left wondering if it "pointed" to the new feed or the old one. I was calling SubmitFeed() multiple times, i.e. trying to resubmit the new feed, to get an "unambiguous" id. Clearly, I will now adopt my own PK but that won't solve the main issue: the ID pointing to the "old" feed. I can't call GetFeedSubmissionList() or GetFeedSubmissionResult(). I need to disregard the ID, resubmit the feed till I get a brand new ID. MWS Support has been "investigating" this for over a month.
– sexybit
Dec 10 '18 at 16:47
add a comment |
I guess I don't understand how you are using it. You submit a feed and then store that id so you can later query to get a feed processing status? You should never use that id as the primary key to your table. You can't guarantee uniqueness as you've found.
– ScottG
Dec 8 '18 at 16:02
Hi ScottG, thanks for replying. Indeed, the intended use is the one you described. The documentation does say that the ID is unique. Anyhow, I have a slew of verified cases in which the same id is returned for a new feed e.g. 12h later and, if queried using GetFeedSubmissionList(), you can see that the SubmittedDate still refers to the first submitted feed. I am just trying to figure out how to handle this whole thing. Right now I'm just disregarding them and retrying SubmitFeed() multiple times till I get a new ID. Thanks for your input.
– sexybit
Dec 9 '18 at 19:46
what is the purpose for calling submitfeed multiple times? I submit a feed and then in a loop, I check every xx seconds to see if it was successful or not. If not successful, I have I data problem, more than likely, so I use my notify process to alert me(the admin) that something is wrong. I really could care less about the feed submission id. I just use that to query the status of the submit request. Once the request is submitted successfully, I'll log it, just so I can have an audit trail (my log has it's own PK ID, it's not feedsubmittionid), but then I don't care about it any more.
– ScottG
Dec 10 '18 at 14:53
At first I wasn't sure if the ID was being "reused" or not. Meaning that if I got the same ID for a new feed I was left wondering if it "pointed" to the new feed or the old one. I was calling SubmitFeed() multiple times, i.e. trying to resubmit the new feed, to get an "unambiguous" id. Clearly, I will now adopt my own PK but that won't solve the main issue: the ID pointing to the "old" feed. I can't call GetFeedSubmissionList() or GetFeedSubmissionResult(). I need to disregard the ID, resubmit the feed till I get a brand new ID. MWS Support has been "investigating" this for over a month.
– sexybit
Dec 10 '18 at 16:47
I guess I don't understand how you are using it. You submit a feed and then store that id so you can later query to get a feed processing status? You should never use that id as the primary key to your table. You can't guarantee uniqueness as you've found.
– ScottG
Dec 8 '18 at 16:02
I guess I don't understand how you are using it. You submit a feed and then store that id so you can later query to get a feed processing status? You should never use that id as the primary key to your table. You can't guarantee uniqueness as you've found.
– ScottG
Dec 8 '18 at 16:02
Hi ScottG, thanks for replying. Indeed, the intended use is the one you described. The documentation does say that the ID is unique. Anyhow, I have a slew of verified cases in which the same id is returned for a new feed e.g. 12h later and, if queried using GetFeedSubmissionList(), you can see that the SubmittedDate still refers to the first submitted feed. I am just trying to figure out how to handle this whole thing. Right now I'm just disregarding them and retrying SubmitFeed() multiple times till I get a new ID. Thanks for your input.
– sexybit
Dec 9 '18 at 19:46
Hi ScottG, thanks for replying. Indeed, the intended use is the one you described. The documentation does say that the ID is unique. Anyhow, I have a slew of verified cases in which the same id is returned for a new feed e.g. 12h later and, if queried using GetFeedSubmissionList(), you can see that the SubmittedDate still refers to the first submitted feed. I am just trying to figure out how to handle this whole thing. Right now I'm just disregarding them and retrying SubmitFeed() multiple times till I get a new ID. Thanks for your input.
– sexybit
Dec 9 '18 at 19:46
what is the purpose for calling submitfeed multiple times? I submit a feed and then in a loop, I check every xx seconds to see if it was successful or not. If not successful, I have I data problem, more than likely, so I use my notify process to alert me(the admin) that something is wrong. I really could care less about the feed submission id. I just use that to query the status of the submit request. Once the request is submitted successfully, I'll log it, just so I can have an audit trail (my log has it's own PK ID, it's not feedsubmittionid), but then I don't care about it any more.
– ScottG
Dec 10 '18 at 14:53
what is the purpose for calling submitfeed multiple times? I submit a feed and then in a loop, I check every xx seconds to see if it was successful or not. If not successful, I have I data problem, more than likely, so I use my notify process to alert me(the admin) that something is wrong. I really could care less about the feed submission id. I just use that to query the status of the submit request. Once the request is submitted successfully, I'll log it, just so I can have an audit trail (my log has it's own PK ID, it's not feedsubmittionid), but then I don't care about it any more.
– ScottG
Dec 10 '18 at 14:53
At first I wasn't sure if the ID was being "reused" or not. Meaning that if I got the same ID for a new feed I was left wondering if it "pointed" to the new feed or the old one. I was calling SubmitFeed() multiple times, i.e. trying to resubmit the new feed, to get an "unambiguous" id. Clearly, I will now adopt my own PK but that won't solve the main issue: the ID pointing to the "old" feed. I can't call GetFeedSubmissionList() or GetFeedSubmissionResult(). I need to disregard the ID, resubmit the feed till I get a brand new ID. MWS Support has been "investigating" this for over a month.
– sexybit
Dec 10 '18 at 16:47
At first I wasn't sure if the ID was being "reused" or not. Meaning that if I got the same ID for a new feed I was left wondering if it "pointed" to the new feed or the old one. I was calling SubmitFeed() multiple times, i.e. trying to resubmit the new feed, to get an "unambiguous" id. Clearly, I will now adopt my own PK but that won't solve the main issue: the ID pointing to the "old" feed. I can't call GetFeedSubmissionList() or GetFeedSubmissionResult(). I need to disregard the ID, resubmit the feed till I get a brand new ID. MWS Support has been "investigating" this for over a month.
– sexybit
Dec 10 '18 at 16:47
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53399295%2famazon-mws-feed-submission-ids-returned-are-not-unique%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53399295%2famazon-mws-feed-submission-ids-returned-are-not-unique%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I guess I don't understand how you are using it. You submit a feed and then store that id so you can later query to get a feed processing status? You should never use that id as the primary key to your table. You can't guarantee uniqueness as you've found.
– ScottG
Dec 8 '18 at 16:02
Hi ScottG, thanks for replying. Indeed, the intended use is the one you described. The documentation does say that the ID is unique. Anyhow, I have a slew of verified cases in which the same id is returned for a new feed e.g. 12h later and, if queried using GetFeedSubmissionList(), you can see that the SubmittedDate still refers to the first submitted feed. I am just trying to figure out how to handle this whole thing. Right now I'm just disregarding them and retrying SubmitFeed() multiple times till I get a new ID. Thanks for your input.
– sexybit
Dec 9 '18 at 19:46
what is the purpose for calling submitfeed multiple times? I submit a feed and then in a loop, I check every xx seconds to see if it was successful or not. If not successful, I have I data problem, more than likely, so I use my notify process to alert me(the admin) that something is wrong. I really could care less about the feed submission id. I just use that to query the status of the submit request. Once the request is submitted successfully, I'll log it, just so I can have an audit trail (my log has it's own PK ID, it's not feedsubmittionid), but then I don't care about it any more.
– ScottG
Dec 10 '18 at 14:53
At first I wasn't sure if the ID was being "reused" or not. Meaning that if I got the same ID for a new feed I was left wondering if it "pointed" to the new feed or the old one. I was calling SubmitFeed() multiple times, i.e. trying to resubmit the new feed, to get an "unambiguous" id. Clearly, I will now adopt my own PK but that won't solve the main issue: the ID pointing to the "old" feed. I can't call GetFeedSubmissionList() or GetFeedSubmissionResult(). I need to disregard the ID, resubmit the feed till I get a brand new ID. MWS Support has been "investigating" this for over a month.
– sexybit
Dec 10 '18 at 16:47