Skip to content

errors: Add 40340 "Integration target address not permitted" - #368

Draft
SimonWoolf wants to merge 1 commit into
mainfrom
add-40340-integration-target-not-permitted
Draft

SimonWoolf wants to merge 1 commit into
mainfrom
add-40340-integration-target-not-permitted

Conversation

@SimonWoolf

Copy link
Copy Markdown
Member

A dedicated code for an integration target that resolves to an address on the IP blocklist, which realtime currently reports as the generic 40300. Realtime needs to tell it apart so it can stop retrying it.

Fixes PUB-4021

🤖 Generated with Claude Code

Reported when an integration's target resolves to an address Ably will not
connect to, such as a private, loopback or link-local one, whether at the time
the integration is created or updated or when Ably connects to deliver to it.

Realtime has reported this as the generic 40300, which says only that the
request was forbidden, and which realtime can't tell apart from other refusals
when deciding whether a failed delivery is worth retrying.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant