On successful run following a failed run, Elementary reports failures from the previous run

[Janiczek]

Describe the bug
On successful run following a failed run, Elementary reports failures from the previous run.

To Reproduce
Steps to reproduce the behavior:

1. Set up Slack reporting via:

- name: Run Elementary
  if: ${{ always() }}
  uses: elementary-data/run-elementary-action@v1.12
  with:
    warehouse-type: snowflake
    profiles-yml: ${{ secrets.PROFILES_YML_NEW }}
    edr-command: |
      edr monitor --slack-webhook ${{ secrets.SLACK_WEBHOOK_URL }}
      edr send-report --slack-token ${{ secrets.SLACK_TOKEN_ELEMENTARY }} --slack-channel-name ${{ secrets.SLACK_CHANNEL_NAME }} --slack-file-name "quality_report_$(date +%Y-%m-%d).html" --select last_invocation

2. Run with failing DBT models
3. Run with working DBT models

Expected behavior
Errors are only reported for the failed run

Actual behaviour
Errors are also reported for the succesful run.

Screenshots
The time reported by Elementary in the below screenshot is from the failed run.

Environment (please complete the following information):

• Elementary CLI (edr) version: 0.16.1
• Elementary dbt package version: 0.19.1
• dbt version you're using 1.10.4
• Data warehouse: snowflake
• Infrastructure details: GitHub Actions (runs-on: aws-small-ubuntu24)

[NoyaOffer]

Hey @Janiczek ! Thanks for raising this,
Was this alert sent on the previous run as well?
Alerts are stored until sent, so this is an expected behaviour, unless they were sent more than once.

[github-actions]

This issue is stale because it has been open for too long with no activity.
If you would like the issue to remain open, please remove the stale label or leave a comment.