- Shipped
- September 12, 2026 at 12:54 AM UTC
- Author
- Kamo
- Commit
- c416c9c
The client knew a provider status called PENDING that the backend never sends, so a sender that was saved but not yet tested fell through to "Not configured". It now reads PENDING_SETUP (still accepting PENDING) and normalises the whole state in one place: the connection summary, when the password last changed, the platform relay and whether the member may manage it. Failures come back as BulkEmailApiError, carrying the HTTP status and, for a 400, the form field the backend named, so the form can put the message on that field and a 403 can be shown as an access state rather than an error. Empty 204s are tolerated, and a save or warm-up write that answers with a bare acknowledgement is followed by a GET instead of being adopted as the state, which is what blanked the form after every save. Adds the warm-up calls: GET and PUT /bulk-provider/warmup and POST /bulk-provider/warmup/reset.