We are currently experiencing delivery failures for our subscriptions. While the notification payload provides valuable information such as the subscription ID and failed item ID, it lacks the essential detail of the delivery failure reason. This information is crucial for us to effectively troubleshoot and resolve delivery issues.
{
"schema_version": "0.0.1",
"subscription_id": "5ba3b46d-5eb5-4ec5-a3c7-8faf6c906014",
"topic": "delivery.failed",
"name": "elegant dragonite",
"result": {
"item_id": "20240826_223522_66_24b7"
},
"timestamp": "2024-08-27T04:09:45+00:00"
}
Proposed Enhancement:
- Include Failure Reason: Add a new field to the notification payload that clearly specifies the reason for the delivery failure. This could include but is not limited to:
- Item Errors: Invalid item format, missing required data, or processing errors.
- Provide Detailed Information: If possible, include additional details related to the failure reason to aid in troubleshooting. For example:
{
"id": "70455fea-1706-499d-8795-dd7c7293f900",
"status": "failed",
"properties": {
"item_id": "20240826_223522_66_24b7",
"item_types": [
"PSScene"
]
},
"created": "2024-08-27T03:56:17.715664Z",
"updated": "2024-08-27T04:09:45.144083Z",
"completed": "2024-08-27T04:09:45.144083Z",
"errors": {
"reason": "Processing failed",
"details": [
"could not collect necessary data for task (code: FAILURE_CODE_UNSCHEDULABLE Harmonize_v1)"
]
},
"outputs": []
}
We believe that incorporating delivery failure reasons into the notification payload will greatly enhance the usability and effectiveness of your service. Thank you for considering this feature request.
