Troubleshooting Respond

Helpful tips for troubleshooting issues in Respond

This page is dedicated to helping you troubleshoot any errors you experience in Respond.

Troubleshooting Errors

There was an error executing your search. Please try again

This error generally populates when there are one or more errors in your overall search. If the error relates to one particular component or filter in your search, this should show as an additional error at the bottom of your Deep Dive, and could be one of the following:

The date range you have supplied is outside the allowed range, if you need data beyond this boundary please contact Lexer

You can up to the last 90 days on content in Lexer Engage. To view data beyond this date range, head into Activity, where you can pull team stats and analyze conversation history across a greater date range. You can also export the data from here for your own analysis. If this data isn’t what you’re looking for, reach out to Lexer Support (support@lexer.io) to discuss other options.

The date you supplied is invalid

If you’ve entered your date into the field manually, this message is to inform you that the format is incorrect. To correct this, the format should be DD/MM/YYYY, and ensuring this is within a 90 day period.

There are no results

No results have been returned in this search. Your search could be looking for something very specific, and there are no mentions with the criteria you’ve selected. Try broadening your search, then gradually honing in by narrowing your list of source types, author names etc. Also check that your filters aren’t conflicting. For example, your Tier 1 filter is looking for content on social media, but you have a Tier 2 filter that’s looking for new mentions in news articles and forum posts.

Issue with your Deep Dive

This error will tell you that one of the filters in your search has been formatted incorrectly, or is likely to restrict your search. To follow, will be a helpful pointer to the part of your search causing this, such as:

Using geographical detail is very limiting

Location filters will only pull in content that has geographical data associated with it. If no location data has been supplied by the page/account/author of the content, then this will not be captured in the search.

One or more of your filters is invalid. Check your query for missing quotes, brackets, ANDs or ORs.

There is an issue with your Boolean in a filter that uses a free text field. Check out our guide to using Boolean language to help correct this. We also recommend using a text editor to clearly spot and fix errors in long strings of Boolean.

HMMM…

Lexer Engage generally throws an error like this when there’s an external issue, and may be followed by:

Page request limit reached

This happens as a result of low engagement with your Facebook Page. Facebook implements rate limits as a means to prevent spammy accounts.

Something went wrong when responding

Usually followed by something more specific to the error - generally the native source (Facebook, Twitter etc) preventing you from responding. This may be because the author has blocked responses from your Page, or the source is down/experiencing difficulties.

Something went wrong performing action

Again, this will usually be followed by a more accurate description of the error, and provide further instruction. For example: “Something went wrong liking object, Facebook may be experiencing issues. Retry after waiting.”

Not seeing the results you were expecting?

First thing’s first - check your filters. They need to be configured properly to pull in relevant results. Check out our guide to Filtering the Inbox for more information.

Unable to respond to content?

This likely boils down to your permissions. If you don’t have access to the account you’re attempting to respond from, this option won’t be available to you from the ‘Engage from account’ dropdown menu. If that’s the case, reach out to your manager, or contact Lexer Support (support@lexer.io) to check and have your permissions updated. Other reasons for being unable to respond to objects, are that it has since been deleted natively (in which case, the text should appear crossed out in Lexer), or the author has blocked you from being able to respond (whereby you’ll be thrown an error message that outlines this).

Content delayed?

Occasionally, you might find messages appear in your Inbox with a delay. You can confirm this by hovering over the age of the object in your queue (in its top right corner, shown in days/hours/minutes), to see the time in which it was processed. Usually, this should display no more than a minute or two, but if it’s more than that, the likelihood is there’s been a delay in it being delivered to Lexer.

We know that it’s common for some content to be sent to us with delay, and the social networks do not notify us if this happens for a small volume of content. However, if we are noticing a large volume of delayed content, or are experiencing other issues, we’ll reach out to you know, and post updates of any performance issues on our Status Page.

Here are some useful links for more information, or to report a problem:

Facebook/Instagram

Twitter

If you are still having trouble, please get in touch

  • Lexer Support live chat in the Lexer platform.
  • Email Lexer Support (support@lexer.io).
Updated:
December 12, 2022
Did this page help you?
Thank you! Your feedback has been received!
Oops! Something went wrong while submitting the form, for assistance please contact support@lexer.io
Welcome to Lexer!
Fundamentals
Getting started
Our glossary
Fundamentals
Getting started
Integrations
Fundamentals
Setup
My account
Fundamentals
Setup
Manage team
Fundamentals
Setup
Group permissions
Fundamentals
Setup
Classifications
Fundamentals
Setup
Out of the box segments
Fundamentals
Setup
Browser guide
Fundamentals
Security
Corporate networks
Fundamentals
Security
Emergency contact
Fundamentals
Security
Multi-factor authentication
Fundamentals
Security
Single sign-on
Fundamentals
Security
Trust and compliance
Fundamentals
Security
Lexer's Identity Resolution
Fundamentals
Identity Resolution
Troubleshooting tech issues
Fundamentals
Troubleshooting
Error code: 503 Service Unavailable
Fundamentals
Troubleshooting
Error code: 401 Unauthorized
Fundamentals
Troubleshooting
Error code: 403 Forbidden
Fundamentals
Troubleshooting
Troubleshooting Activate
Fundamentals
Troubleshooting
Troubleshooting Respond
Fundamentals
Troubleshooting
Help! My data is missing from the Hub
Fundamentals
Troubleshooting
Understanding APIs at Lexer
Data
Data Onboarding
Providing JSON data to Lexer
Data
Data Onboarding
Providing CSV data to Lexer
Data
Data Onboarding
Upload using SFTP
Data
Data Onboarding
Upload using S3
Data
Data Onboarding
Lexer data specification
Data
Lexer Data Specification
Customer data specification
Data
Lexer Data Specification
Commerce data specification
Data
Lexer Data Specification
Marketing data specification
Data
Lexer Data Specification
Compliance data specification
Data
Lexer Data Specification
Data Formatting and Validation
Data
Getting Started with APIs
Authentication and API token creation
Data
Getting Started with APIs
Rate Limits
Data
Getting Started with APIs
Response codes and common errors
Data
Getting Started with APIs
Product imagery
Data
Getting Started with APIs
Currency conversion
Data
Getting Started with APIs
Lexer’s APIs overview
Data
Lexer’s APIs
Dataset management in the Hub
Data
Dataset management
Chatbox user API
Data
Lexer’s APIs
Activity API
Data
Lexer’s APIs
Visualize API
Hidden from nav
Profile Read API
Data
Lexer’s APIs
Lexer Javascript Tag basics
Data
Lexer Javascript Tag
Lexer Javascript Tag technical guide
Data
Lexer Javascript Tag
Lexer Javascript Tag use cases
Data
Lexer Javascript Tag
dataLayer configuration: Shopify
Data
Lexer Javascript Tag
Customer segment CSV export
Data
Data off-boarding
Export to CSV
Data
Data off-boarding
Data in Lexer's CDXP
Understand
Customer Data
Lexer's attributes
Understand
Customer Data
Attribute value types
Understand
Customer Data
Data source - CRM
Understand
Customer Data
Data source - Transactions
Understand
Customer Data
Data source - Email
Understand
Customer Data
Partner data - Experian
Understand
Customer Data
Partner data - Mastercard
Understand
Customer Data
Partner data - Roy Morgan
Understand
Customer Data
GDPR and CCPA requests
Understand
Customer Data
Upload data files
Understand
Customer Data
File upload API
Understand
Customer Data
Data provision and schemas
Understand
Customer Data
Segment overview
Understand
Segment
Creating segments
Understand
Segment
Smart Search
Understand
Segment
Export attribute results
Understand
Segment
Contact a customer
Understand
Segment
Fixing a disabled segment
Understand
Segment
Profile tab
Understand
Segment
Compare segments
Understand
Compare
Compare attributes
Understand
Compare
Activate overview
Engage
Activate
Ongoing activations
Engage
Activate
Audience splits
Engage
Activate
A/B splits
Engage
Activate
Control group splits
Engage
Activate
Inbox filtering
Engage
Respond
Ignored Senders
Engage
Respond
Forms for service
Engage
Respond
Workflow states
Engage
Respond
Bulk changes
Engage
Respond
Scheduled replies
Engage
Respond
Message templates
Engage
Respond
Customer profiles
Engage
Respond
Grouped messages
Engage
Respond
Automation rules
Engage
Respond
Redact messages
Engage
Respond
Track overview
Measure
Track
Activity overview
Measure
Activity
Team report
Measure
Activity
Cases report
Measure
Activity
Listen overview
Measure
Listen
Searching in Listen
Measure
Listen
Tier filters
Measure
Listen
Boolean search
Measure
Listen
Saved dives
Measure
Listen
Email notifications
Measure
Listen
Twitter data
Measure
Listen
Facebook data
Measure
Listen
Instagram data
Measure
Listen
Visualize overview
Measure
Visualize
Curate feed
Measure
Visualize
Report overview
Measure
Report