Hi, My CI failed two days in a row for this error despite of the fact that in the Elementary report, everything is OK. Does anyone have same issue and know what's going on? I dont' have any Elementary or DBT test with this condition :

updated_at

none is not an allowed value (type=type_error.none.not_allowed)

07:05:45  Completed successfully
07:05:45  
07:05:45  Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1
2024-03-02 07:05:45 — INFO — Running dbt --log-format json run-operation elementary.log_macro_results --args {"macro_name": "elementary_cli.get_pending_alerts", "macro_args": {"days_back": 1, "type": null}} --project-dir /home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/elementary/monitor/dbt_project --profiles-dir ./ci
Traceback (most recent call last):
  File "/home/runner/work/data-transformation/data-transformation/.venv/bin/edr", line 8, in <module>
    sys.exit(cli())
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/elementary/cli/cli.py", line 67, in invoke
    return super().invoke(ctx)
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/click/core.py", line 1635, in invoke
    rv = super().invoke(ctx)
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/elementary/monitor/cli.py", line 364, in monitor
    success = data_monitoring.run_alerts(
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/elementary/monitor/data_monitoring/alerts/data_monitoring_alerts.py", line 292, in run_alerts
    alerts = self._fetch_data(days_back)
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/elementary/monitor/data_monitoring/alerts/data_monitoring_alerts.py", line 84, in _fetch_data
    return self.alerts_api.get_new_alerts(
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/elementary/monitor/api/alerts/alerts.py", line 31, in get_new_alerts
    pending_alerts = self.alerts_fetcher.query_pending_alerts(days_back=days_back)
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/elementary/monitor/fetchers/alerts/alerts.py", line 49, in query_pending_alerts
    return [
  File "/home/runner/work/data-transformation/data-transformation/.venv/lib/python3.8/site-packages/elementary/monitor/fetchers/alerts/alerts.py", line 50, in <listcomp>
    PendingAlertSchema(**result)
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for PendingAlertSchema
updated_at
  none is not an allowed value (type=type_error.none.not_allowed)
Error: Process completed with exit code 1.

Hi @Kim , this looks like a bug we solved in our recent release, can you try to upgrade to our latest version? 0.14.1

Thanks @Ella Katz It works. 🎉 Can you explain me what was the issue?

Hey @Kim, chiming in here 🙂 We did a refactor on the way our alerts work behind the scenes, and there was a small bug with the source freshness alerts new schema. It could be that you had a failure with a source freshness that was resolved and this is why you don't see it in the report 🙂

Ok thanks 🙏