Reports — Troubleshooting
Error: "Report not generated. Timed out"
Message: Report not generated. Timed out.
What it means: Building the report took longer than the maximum allowed time. The system aborted execution to avoid blocking resources.
Possible causes:
- The date range is too large, or there are too many metrics in one report
- One of the data sources is responding slowly
- A complex report configuration with many calculated fields
- High system load at the moment
What to do:
- Split the report into several with smaller date ranges (e.g., monthly instead of yearly)
- Reduce the number of metrics and groupings in a single report
- Make sure all data sources are active and accessible
- Run the report at an off-peak time (e.g., early morning or late evening)
- If the report has a schedule — increase the interval to 6–12 hours
Retry the run: yes
Reconnection required: no
When to contact support: If the timeout occurs even for a report with a single source and a 7-day range, or if the same report used to build successfully before.
What to send: Report name, data sources, date range, number of metrics, error time, screenshot of the error.
Error: "Report generated, but the result is empty"
Message: Report generated, but the result is empty. Check the report settings and data sources.
What it means: The system successfully queried all sources but got no data matching the report's conditions.
Possible causes:
- There genuinely is no data in the connected sources for the selected period
- The report filters exclude all available data
- The data source was disconnected or its content was cleared
- The selected ad account or account had no activity during the specified period
What to do:
- Check whether there's data in the source directly (log in to the ad account/CRM and check the same period)
- Widen the date range
- Remove or loosen the filters
- Make sure the correct account is selected from the dropdown list
- Check whether the source connection token has expired
Retry the run: yes (after changing settings)
Reconnection required: possibly (if the token expired)
When to contact support: If there's definitely data in the source, the report settings are minimal (no filters, wide range), and the result is still empty.
What to send: Report name, data sources, date range, list of applied filters, screenshot of the error and a screenshot with data directly from the source.
Error: "Sheet not found. It may have been deleted or renamed"
Message: Sheet not found. It may have been deleted or renamed.
What it means: The Google Sheets sheet specified as the target for the report export no longer exists or is unreachable via the saved link.
Possible causes:
- The sheet was deleted by the owner or an editor
- The sheet was renamed
- The sheet was moved to a different folder
- You no longer have access to this sheet (permissions were revoked)
- The link to the sheet in the report settings is corrupted
What to do:
- Go to Google Sheets and check whether the sheet exists at the old link
- If the sheet was deleted — restore it from the Google Drive trash (available for 30 days)
- If the sheet was renamed or moved — copy the new link
- Update the link in the report settings in Lightlead
- Save the changes and rerun the report
Retry the run: yes
Reconnection required: no (updating the link is enough)
When to contact support: If the sheet exists at the link and you have access to it, but Lightlead still can't find it.
What to send: Report name, link to the target sheet, your access level to the sheet (screenshot from Google Sheets "Share" settings), error time, screenshot of the error.
Error: "Write conflict. The sheet is being edited by another user"
Message: Write conflict. The sheet is being edited by another user. Try again later.
What it means: Lightlead tried to write data to the Google Sheets sheet, but another user was actively editing the same sheet at that moment. The system delayed the write to avoid losing data.
Possible causes:
- Another user is manually making changes to the sheet
- Two reports are configured to write to the same sheet with the same run time
- Another service or script is writing to this sheet at the same time
What to do:
- Check whether the sheet is open for editing by you or a colleague
- Close the sheet for all users
- Make sure other reports in Lightlead aren't configured to write to the same sheet at the same run time
- Retry the report in 1–2 minutes
- For recurring reports — stagger the run times by at least 15 minutes
Retry the run: yes
Reconnection required: no
When to contact support: If the conflict occurs regularly even when no one is editing the sheet, or if the report stopped exporting entirely after fixing the data.
What to send: Report name, link to the sheet, error time, scheduled report run time, screenshot of the error.
Error: "Invalid range. The specified range is outside the sheet's bounds"
Message: Invalid range. The specified range is outside the sheet's bounds.
What it means: The report settings specify a cell range (e.g., A1:Z1000) that exceeds the sheet's actual size or contains a syntax error.
Possible causes:
- The sheet shrank after data was cleared or deleted
- The range has an error (e.g., references non-existent columns)
- The sheet was replaced with a new one with fewer columns
- The report settings hard-code a range, and the sheet's structure changed
What to do:
- Open the sheet in Google Sheets and check its actual size
- In the report settings, change the range to a correct one matching the sheet's actual structure
- It's recommended to use relative ranges (e.g., starting from the first empty row)
- Save the changes and restart the report
Retry the run: yes
Reconnection required: no
When to contact support: If you specified a correct range but the error persists, or if the settings reset themselves after saving.
What to send: Report name, link to the sheet, the range specified in the settings, screenshot of the error, screenshot of the sheet's structure.
Error: "Failed to save report settings"
Message: Failed to save report settings. Try again later.
What it means: The system couldn't write the report configuration. Your changes were not applied.
Possible causes:
- A temporary glitch in the report configuration service
- A version conflict: another user, or you in a different tab, is editing the same report at the same time
- A limit on the number of reports in the plan
- Invalid data in one of the fields that failed validation
What to do:
- Refresh the page and try saving again
- Make sure the report isn't open in another browser tab
- Check that all required fields are filled in correctly
- Check the report limit in your plan
- Copy the settings to a temporary file, create a new report, and transfer them there
Retry the run: no (the report isn't configured yet)
Reconnection required: no
When to contact support: If the error persists after reloading and creating a new report, or if you can't save any report at all.
What to send: Report name, list of fields and values you tried to save, error time, your plan, screenshot of the error.