bulk-submit-status returns 500 when a manifest output URL 404s

[johngrimes]

Summary

When a bulk-submit manifest contains an output file URL that 404s, $bulk-submit-status returns 500 OperationOutcome instead of a status manifest with error output as described in the spec.

Environment

• Server: https://demo.pathling.app/fhir (pathling-demo)
• Spec: https://hackmd.io/NlrhAtppTIWGfHaJDfhzpQ.md

Steps to Reproduce

1. Create submission to Pathling demo and submit manifest https://bulk-submit-provider.smarthealthit.org/api/manifests/2.
2. Mark submission complete.

Observed

• Pathling logs:
  • Failed to download file from https://bulk-submit-provider-5dcd741b9746.herokuapp.com/exports/2/CarePlan.ndjson: HTTP 404
  • Submission 9c2bb182-cce8-474c-bef5-d05221162540 completed with errors
  • Job ID: 904c5f83-7eee-4117-9262-d7f99da8613d
• $bulk-submit-status kick-off returns 500 OperationOutcome: Submission failed: Unknown error.
• Polling /fhir/$job?id=904c5f83-7eee-4117-9262-d7f99da8613d from the origin returns 500 OperationOutcome Unexpected error occurred.

Expected

Per spec, status polling should return a status manifest (200) with error entries pointing to OperationOutcome files tied to the manifestUrl. A missing output file should be reflected in the status manifest, not a 500 error.

Additional details

• Manifest 2 output entry that 404s: https://bulk-submit-provider-5dcd741b9746.herokuapp.com/exports/2/CarePlan.ndjson
• Submission ID: 9c2bb182-cce8-474c-bef5-d05221162540