Refactor file retry functionality and update API endpoint #596
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was to remove a redundant retry/resubmit function that was from an initial PR to manage this from the community. This was replaced by the new resubmit and delete function some time back. The PR addresses this, but during dev I discovered another error. When a file was resubmitted, its status was not changing immediately in the document status table. This was because a net new json document was being created for the file. The reason this was happening is because the document key is the encoded full path of the file including the container, 'upload'. On resubmission it was just using the file name, hence another document. I have added the full path and verified it works as expected now