70001: Integration invocation failed

An integration could not invoke its configured target: Ably either could not reach the target, or reached it but could not deliver the data. The specific failure depends on the integration type and is named in the error message.

What you should do

Start with the underlying error in the message: it names the specific failure for the integration type. For a webhook or other HTTP target, that is typically a refused or reset connection, a timeout, a DNS lookup failure, or a TLS certificate the connection won't accept. For a queue or streaming target such as Kafka, Kinesis, or SQS, it is typically a failure to connect to the service or to deliver the message. Use it to check that the configured target is reachable, correctly addressed, and accepting data from Ably.

Ably retries failed invocations with a backoff, so a brief outage recovers on its own. Persistent failures mean the target stays unavailable and data is not being delivered.

Why it happens

When a message matches one of your integrations, Ably invokes the target you configured. This error means that invocation failed: Ably could not connect to the target, or connected but could not deliver to it. Where the target does respond but rejects the request, the error is reported as 70002 instead.

What you'll see

The error is reported with code 70001. The message names the operation that failed and includes the underlying error, in a form that depends on the integration type: for an HTTP target, Webhook operation failed (post operation failed); err = <detail> or POST failed: <detail>, carrying HTTP status 503; for other integration types, a target-specific message such as Kafka client was unable to send the message: <detail>.