Register error code 103009 for push not enabled on a cluster

errors/codes/103009.md

@@ -0,0 +1,22 @@
+---
+code: 103009
+identifier: push_not_enabled_for_cluster
+title: Push notifications not enabled for the cluster
+summary: The push notification was not accepted for delivery because push notifications are not enabled in the cluster handling the request. On a dedicated cluster, push notifications have to be turned on by Ably before any can be sent.
+---
+
+## What you should do
+
+Ask [Ably support](https://ably.com/support) to enable push notifications on the cluster. It is not something you can turn on yourself, so the error will not clear on its own and retrying will not help. Once push is enabled, publishing works without any change to your application, its push configuration, or its existing device registrations.
+
+## Why it happens
+
+Push notifications are enabled per cluster, and only Ably can enable them. Ably's main cluster always has the feature enabled, so the error only arises on a dedicated cluster where push was not included when the cluster was provisioned and has not been added since.
+
+Registering devices and subscribing them to channels are handled separately and keep working, so the usual symptom is that every push publish fails while registrations and subscriptions continue to succeed.
+
+## What you'll see
+
+The error is reported with code 103009 and HTTP status 500. The message is `Push notifications are not enabled for this cluster. Please contact Ably support to enable push.`
+
+A push notification triggered by publishing to a channel has no response for you to inspect, because the channel publish itself still succeeds. Those failures are reported on the `[meta]log:push` metachannel, which carries [push events and errors that are not otherwise returned to clients](https://ably.com/docs/push).

protocol/errors.json

@@ -1307,6 +1307,11 @@
       "title": "Push transport credentials invalid",
       "summary": "A push notification could not be sent because the credentials configured for the target platform were rejected or had expired, such as an expired APNs certificate."
     },
+    "103009": {
+      "identifier": "push_not_enabled_for_cluster",
+      "title": "Push notifications not enabled for the cluster",
+      "summary": "The push notification was not accepted for delivery because push notifications are not enabled in the cluster handling the request. On a dedicated cluster, push notifications have to be turned on by Ably before any can be sent."
+    },
     "104000": {
       "identifier": "streamed_message_finalize_failed",
       "title": "Streamed message could not be finalized",