When the capability statement is generated during background jobs, we try and build a url using the action context which is null during backgrounds jobs like bulk-delete
Update the title of the PR to be succinct and less than 65 characters
Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
Description
When the capability statement is generated during background jobs, we try and build a url using the action context which is null during backgrounds jobs like bulk-delete
Related issues
Addresses [issue AB#122137].
Testing
Manual testing of bulk-delete to repro the issue
FHIR Team Checklist
Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)