michelpmcdonald
commented
2 years ago script used find External service unavailable 526 submission rejects:
#go after external service errors
jss = Form526JobStatus.where(status: 'exhausted', error_message: "External service unavailable", updated_at: 5.days.ago.utc..).order(:updated_at)
jss.each do |js|
if js.bgjob_errors.to_s.include?('GUID:')
#puts "Vetsapi id: #{js.id}, Has evss error guid: #{js.bgjob_errors.to_s.include?('GUID:')}"
#next to last entry in bgjob_errors has the "last" evss error tracking guid
#puts "Err key #{js.bgjob_errors.keys[-2]}"
#iterate the job run history list from newest run attempt to oldest, pick out the newest evss error tracking guid
js.bgjob_errors.keys.reverse.each do |bgerr_key|
if js.bgjob_errors[bgerr_key].to_s.include?('GUID:')
puts "Vetsapi id: #{js.id}, #{js.bgjob_errors[bgerr_key]['timestamp']}, #{js.bgjob_errors[bgerr_key].to_s[-49..-7]}"
break
end
end
puts ""
end
end; nil
saderagsdale
Sev 1 because we are back to significant number of claims being silently dropped.
Impact: As of July 7th, we have hit this issue 3873 times since June 1st
Starting on June 13th(confirm date, have script) "PIF in Use" claim rejections have stopped, but looks like they are replaced with "External service unavailable".
Related, we just enabled sending out failed submission notification to vet who hit the PIF in Use error, but now PIF in use has disappeared. Need to decide if we need to send out notifications for this newish "External service unavailable"..error, but first we need to figure out if the "External service unavailable" is something we can somehow address without involving the vet themselves, but it's hard to know because EVSS dos not return the underlying error behind the External service unavailable(see below)
It looks like EVSS masks the actual underlying issue in cases when they return a External service unavailable(ie raw form526.submit.establishClaim.serviceError error code in their response jason). I have to reach out to them, give them the claim rejection guid(from their error response json) and they have to manually look up the actual error. So fro example, i gave them reject GUID d4a4a9ff-c1e3-4701-aaad-0601b2bb468a, and the underlying error the received from their external upstream service is: