Troubleshooting AI Issues
We've collected common problems that come up when working with the AI assistant and how to solve them.
The AI doesn't understand the request
Symptom: The AI replies "I can't understand the request," "Please clarify what you mean," or gives an irrelevant answer.
Possible causes and solutions:
Too generic a request — "What's up with the ads?"
- Add specifics: the metric, the period, the source
- Correct: "How much did we spend on Meta Ads yesterday?"
Metric not supported — requesting a metric that isn't in the API
- Check the available metrics in the report builder
- Use standard names: spend, clicks, impressions, conversions
Request too long — over 500 characters
- Split it into several shorter requests
The AI can't get the data
Symptom: "Couldn't retrieve data," "Source unavailable," "No data for this period."
Solutions:
- Source not connected — check its status in the Integrations section
- Auth token expired — reconnect the source manually
- No data for the period — there genuinely wasn't any activity during that period
- API delay — the data hasn't reached the platform's API yet
Today's data
Data for the current day may be incomplete due to API update delays. The AI warns about this. If you need accurate data, request a period ending yesterday.
The AI doesn't perform the action
Symptom: The AI refuses to create/refresh a report or set up an alert.
Solutions:
- Insufficient permissions — the Analyst or Observer role doesn't allow changing data
- Ask the workspace owner to upgrade your role
- Action not confirmed — the AI was waiting for confirmation and canceled due to timeout
- Repeat the request and reply "Yes" to the confirmation
- Report/alert limit — the workspace limit has been reached
- Delete unused reports or alerts
Slow response
Symptom: The AI takes longer than 30 seconds to respond.
Solutions:
- Large data volume — the request covers many entities
- Narrow the period or add a filter (specific campaign, source)
- Source API delay — some platforms respond slowly
- Wait and repeat the request
- Peak load — many simultaneous requests in the workspace
- Wait 1–2 minutes and try again
Data doesn't match
Symptom: The data in the AI's answer doesn't match what you see in the ad account.
Solutions:
- Different time zones — check the time zone in LightLead settings and in the ad account
- API delay — data in the API updates more slowly than in the ad platform's interface
- Different attribution models — the ad account and LightLead may use different attribution models
- Platform-specific API quirks — some metrics are calculated differently via the API
Meta Ads and data discrepancies
The Meta Ads API can show data that differs from Ads Manager. For more details, see Meta Ads Data Discrepancies.