# Reporting data availability and warning logs

Check reporting data availability and inspect unresolved reporting warnings with Developer access.

*Release 3.3 · admin, developer*

**Reports** · **Inside Dev Console › Tools › Logs › Report Logs** · **Settings › General Settings › Admin**

## What it is

**Report Logs** lists unresolved reporting configuration warnings. Developers can use it alongside the data-availability information in **Reports** to investigate missing or inconsistent figures. Administrators can collect the affected report, period and filters for Powerfront to check.

## Who uses it and why

- Developers with the **Developer** role inspect reporting warnings and acknowledge resolved issues.
- Administrators check the selected reporting period and ask Powerfront to investigate setup or refresh problems.

## Where to find it

Open **Reports** to read data-availability information for the selected website.

With **Developer** access, open **Inside Dev Console**, then **Tools › Logs › Report Logs**. Reporting enablement is managed by Powerfront at **Settings › General Settings › Admin**.

## How it works

1. In **Reports**, select the correct website and read the available data period beside the report heading.
2. Check that the period you are investigating falls within that coverage. A message that no data is available means the workspace has no usable availability range for that selection.
3. With **Developer** access, open **Report Logs** and inspect the warning time, type and message.
4. Investigate the cause with Powerfront. Only after it has been addressed, select **Mark as Resolved** to remove the warning from the unresolved list.

The listed warning types include **Time Zone Mismatch**, **Sales Attribution Mismatch**, **Advanced Reports Disabled** and **Incorrect Default Database**. Powerfront can investigate the reporting setup behind these warnings.

Marking a warning as resolved acknowledges the log entry. It does not repair configuration or refresh missing data.

## Configure it

Powerfront can enable reporting and check its setup for your website. Someone with the **Settings** or **Manager** role can check your **Reports** and **Developer** roles at **Settings › Account › Operators**, according to the tasks you perform.

Report dates, website time-zone settings and sales attribution can affect comparisons. Include those details when asking Powerfront to investigate a discrepancy.

### Settings

| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Enable Reports | Settings › General Settings › Admin | website | Off | Powerfront, on request | Makes the website available in the reporting workspace when reporting is configured. |

### Permissions

| Permission | Lets you |
|---|---|
| Developer | Read unresolved reporting warnings and mark a warning as resolved. |
| Reports | Open the reporting workspace and its data-availability information. |

## Limits and good to know

- Historical reporting can lag live activity. The displayed availability range is a coverage indicator, rather than a guarantee that every recent record is complete.
- **Report Logs** shows unresolved warnings, not all past warnings or every possible refresh failure.
- An empty warning list does not establish that reporting is fully up to date.
- Reporting warnings are separate from operator action history and conversation audit search.
- Older and current report versions can use different filters and calculations. Compare the report name, period, scope and definitions before treating a difference as a fault.

## Depends on and works with

### This feature uses

- **Configured in** Admin settings and feature switches (managed by Powerfront): Powerfront manages reporting enablement and setup.
- **Configured in** [Roles and permissions](ADM-008.md): Developer and Reports roles grant different diagnostic and reporting access.
- **Related** [Website and regional settings](ADM-004.md): Website timezone settings help investigate a Time Zone Mismatch warning.
- **Related** [Sales attribution to conversations and operators](COM-021.md): Sales attribution settings help investigate a Sales Attribution Mismatch warning.
- **Related** [Report selection and filters](REP-001.md): Check the selected report and its data availability when investigating missing figures.
- **Related** [Reports data and metric definitions](REP-002.md): Metric definitions help distinguish reporting coverage issues from different counting rules.

### Used by

- **Related** [Reports data and metric definitions](REP-002.md): Data availability and warning logs help investigate missing or inconsistent report figures.

## FAQ and troubleshooting

### Why are today's reports behind live activity?

Historical reports depend on refreshed reporting data. Check the displayed availability period and ask Powerfront to investigate if it has stopped advancing.

### Why can I not open Report Logs with the Reports role?

The diagnostic view requires **Developer** access. The **Reports** role grants the reporting workspace, rather than its developer diagnostics.

### Does Mark as Resolved fix the report?

No. It acknowledges the warning. Address the cause before marking the entry resolved.

### Why are figures different in an older report?

First align the dates, time zones, scope and metric definitions. Older and current reports are not guaranteed to calculate every measure in the same way.

### What should I send Powerfront about a discrepancy?

Provide the website, report name, date range, selected filters, displayed data availability and relevant warning type. Include the expected result and the result you received.