CADC-16019 catch runtime exception when unable to get the recursive set node job - #48
Merged
Merged
Conversation
aratikakadiya
approved these changes
Sep 23, 2026
This file contains hidden or 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
2 participants
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.
When a DOI is minted, it creates a recursive set node job to set the appropriate permissions for a minted DOI, and the job url is added to the DOI node properties. The next GET of the DOI after it's minted checks for the job url, and if if finds a job url tries to get the job phase, which throws a runtime if the job can't be retrieved. The runtime causes the DOI to be missing from a user's list of DOI's Data Publications, and a user thinks their DOI has been deleted.
Catch the runtime and set the job phase to error.
Plus some other cleanup.