An error passed through from Buffer's legacy REST API.
On the way out. This type exists only because some mutations still forward to that API. It is never returned by the tag mutations, and will be removed from their payloads. The post mutations can still return it, so keep handling it there for now.
Do not select it in new operations. Select ... on MutationError { message }
instead, which every error type implements and which keeps working when this one
goes away.
Error code from the REST API response - https://buffer.com/developers/api/errors
Deprecation reason: Being retired along with Buffer's legacy REST API. Select `... on MutationError { message }` to handle errors generically, or the specific recoverable error members of the payload.
Link to our Help center from the REST API response
Deprecation reason: Being retired along with Buffer's legacy REST API. Select `... on MutationError { message }` to handle errors generically, or the specific recoverable error members of the payload.
An error message from the REST API response that we proxied here
Deprecation reason: Being retired along with Buffer's legacy REST API. Select `... on MutationError { message }` to handle errors generically, or the specific recoverable error members of the payload.