When using the Talkative platform, you may encounter some error codes. This guide will provide some more context on any errors and what you need to do to resolve them.
Error’s
502
A 502 error is a message from our load balancer, usually indicating that a request took too long or that too much data was being processed at once. In rare cases, it can also occur if one of our systems temporarily encounters an issue. This error is most often seen on data-heavy pages or reports, especially for larger accounts. It doesn’t necessarily mean something is wrong, just that the system couldn’t complete the request in time.
If you only see this error occasionally, simply refresh the page and try again. If the error appears frequently or across multiple users, please let our support team know so we can investigate further.
500
A 500 error indicates that something went wrong on our side while processing your request. It usually means the system encountered an unexpected condition that it couldn’t complete. In some cases, a 500 error can point to a bug or configuration issue.
These errors are automatically tracked in our monitoring system, which helps our support team review and resolve the root cause quickly.
If you see a 500 error, please let our support team know when and where it appeared. For security reasons, the message won’t include technical details, but our team can investigate the logs in Sentry to identify what went wrong.
422
A 422 error occurs when the system can’t process your request because some of the information sent wasn’t valid. This means the data didn’t meet the required format or rules during validation.
This can occur when submitting information through a form or API. In most cases, the application will display a clear message explaining what needs to be fixed. However, if you’re working directly with an API endpoint, you may need to check the network response in your browser’s developer tools to see the exact validation errors.
To resolve this:
- Double-check that all required fields are filled in correctly.
- If using ECS or another API, make sure the data or customer journey being sent is valid.
- If the issue continues, try clearing your browser’s cookies and cache before retrying.
419
Sometimes, when completing a form such as a login or password reset, you may see a 419 error. This occurs when your CSRF (Cross Site Request Forgery) token has expired.
CSRF tokens are short-lived security tokens issued by our server and linked to your session. When one expires, your browser’s stored token is no longer valid. This is normal behaviour and not an error with Talkative systems.
To fix this, perform a hard refresh (Ctrl + Shift + R in Chrome) or clear website data. If the issue persists, try an incognito window.
This error is rare but can occur more often if you use multiple accounts across different Talkative tenants. Regularly clearing your browser cache and storage helps reduce occurrences.
403
A 403 Forbidden error appears when you don’t have permission to access a particular page or resource. This happens when a permission check fails. For example, if you try to access a feature, page, or interaction that your account doesn’t have rights to view. It can also occur if a resource has been locked or is no longer available, such as an old interaction. If you believe you should have access, please contact your account holder so they can review your permissions and unlock access if appropriate.