aliases/implications: remove 'error' state.
Remove the error status from aliases and implications. Aliases and implications normally shouldn't fail because they're validated beforehand. If they do, just let the delayed job itself record the failure. Also disable the delayed job from retrying if the alias/implication somehow fails.
This commit is contained in:
@@ -98,8 +98,6 @@ class DText
|
||||
"The #{obj.relationship} ##{obj.id} [[#{obj.antecedent_name}]] -> [[#{obj.consequent_name}]] has been rejected."
|
||||
elsif obj.is_pending?
|
||||
"The #{obj.relationship} ##{obj.id} [[#{obj.antecedent_name}]] -> [[#{obj.consequent_name}]] is pending approval."
|
||||
elsif obj.is_errored?
|
||||
"The #{obj.relationship} ##{obj.id} [[#{obj.antecedent_name}]] -> [[#{obj.consequent_name}]] (#{relationship} failed during processing."
|
||||
else # should never happen
|
||||
"The #{obj.relationship} ##{obj.id} [[#{obj.antecedent_name}]] -> [[#{obj.consequent_name}]] has an unknown status."
|
||||
end
|
||||
|
||||
Reference in New Issue
Block a user