Fields removed in schema messageObject: [newsletter_id action_id type created id trigger_event_id tracked_responses failure_message content_id recipient parent_…

What changed

Fields removed in schema messageObject: [newsletter_id action_id type created id trigger_event_id tracked_responses failure_message content_id recipient parent_action_id campaign_id customer_identifiers forgotten customer_id deduplicate_id metrics subject broadcast_id message_template_id] Affected surface: schema messageObject. Root cause: schema `messageObject`. Detected at Tue, 21 Apr 2026 04:55:00 UTC UTC.

Diff

{
  "path": "schema messageObject",
  "removed_fields": [
    "newsletter_id",
    "action_id",
    "type",
    "created",
    "id",
    "trigger_event_id",
    "tracked_responses",
    "failure_message",
    "content_id",
    "recipient",
    "parent_action_id",
    "campaign_id",
    "customer_identifiers",
    "forgotten",
    "customer_id",
    "deduplicate_id",
    "metrics",
    "subject",
    "broadcast_id",
    "message_template_id"
  ],
  "schema_path": "schema messageObject"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Recommended action

Diff your serializers against the new schema. The diff above shows what moved.