Based on the knowledge sources, this behavior is expected. The

--days-back

parameter affects how much historical data is included in the report, but it doesn't change what's shown in the main page summary or Slack notifications. When you run

edr send-report --days-back 30

, the report will include test data from the past 30 days, which you can see in the detailed sections of the report. However, the main page of the report and Slack notifications will still show the most recent test results. This is consistent with how several users have experienced the tool: 1. One user had to place the

--days-back

parameter after the

send-report

command rather than between

monitor

and

send-report

to get it to work properly [Link to Slack conversation](https://slack.com/archives/C02CTC89LAX/p1674155311053909). 2. Another user confirmed that when using the correct parameter placement, they could see "Last 30 Days" in the upper right corner of the report [Link to Slack conversation](https://slack.com/archives/C02CTC89LAX/p1674155311053909). If you're not seeing "Last 30 Days" in the upper right corner of your report, you might want to check the placement of your

--days-back

parameter in your command. Make sure it's placed after the

send-report

command, like this:

edr monitor send-report --days-back 30

Instead of:

edr monitor --days-back 30 send-report

@Ondra Paul may I ask you for the dbt, Databricks adapter and Elementary versions you're using? We see other users experiencing sudden issues with Databricks, so if everything's working for you it can help us find the root cause 🙌 Thanks in advance!