Improvement: Error Details Added to SNS Job Status Notifications

When a packaging job fails, the AWS SNS notification message now includes error_code and error_message fields directly in the payload.

Previously, an ERROR status notification indicated that a job had failed but provided no details about the cause. Customers had to make a separate API call to retrieve the job status and inspect the error. With this update, the failure reason is delivered immediately alongside the status change event, enabling faster automated alerting, triage, and retry logic in downstream workflows.

Updated SNS Notification Payload (ERROR status example):

json

{
  "site_id": "XXXX",
  "job_id": 12345,
  "job_status": "ERROR",
  "error_code": "E8005",
  "error_message": "Failed to segmenting and DRM packaging.",
  "user_data": {},
  "reg_time": "2026-03-10T01:00:00Z",
  "start_time": "2026-03-10T01:00:05Z",
  "update_time": "2026-03-10T01:02:30Z"
}

• error_code and error_message are populated only when job_status is ERROR; they are omitted or null for all other statuses

• For error codes where the cause can be resolved by the customer (e.g., invalid input file, unsupported codec, S3 access denied), the message provides actionable context directly

• For internal server-side errors, the message indicates to contact the Helpdesk

No action is required for existing notification integrations — the new fields are additive and backward compatible. However, if your SNS consumer uses strict schema validation, you may need to update it to accept the new fields.