- Ably FAQs
- Ably error codes
- Client errors
-
Account billing and packages
-
General
-
Realtime API and client libraries
-
Troubleshooting
-
Channels
-
REST API and client libraries
-
Ably error codes
-
Account and app setup and configuration
-
Ably architecture, transports, and security
-
Performance and Redundancy
-
Push Notifications
-
Integrations
-
Migrating to Ably from an existing service
Error code: 40400 - Not found
If you see this error, it means that that resource you are trying to access (which could be anything i.e. the ably app, client, device or connection etc) does not exist.
Resolving this error -
- This is a very generic error code. However, the error text when this error is raised should be self explanatory for you to understand which is the resource you've requested that doesn't exist.
- If you are still unable to solve it, reach out to us and we'll be happy to help you out.
Specific examples of this error include:
No application found with id
This error may occur when attempting to authenticate using an Ably API key or an Ably token, and it will be accompanied by an Ably app id e.g.
No application found with id 7YfamQ
This indicates that the specified app id cannot be found, either because it does not exist in the current environment (if a custom environment is being utilised) or because the app id itself is incorrect. Additionally, be mindful of case sensitivity, as the format of the app id must match exactly.
No key found with id
Similar to No application found with id this error may occur when attempting to authenticate but is related to the API key id being incorrect. As with the app id be mindful of case sensitivity, as the format of the key id must match exactly