@tsteur opened this Issue on March 28th 2022 Member

To reproduce, set below config settings:

[General]
rearchive_reports_in_past_last_n_months = "last1"
rearchive_reports_in_past_exclude_segments = 1
process_new_segments_from = "editLast30"
enable_general_settings_admin = 0
enable_browser_archiving_triggering = 0
browser_archiving_disabled_enforce = 1
enable_create_realtime_segments = 0
  • Then create a segment
  • Then request a date range from 1 year ago.
  • You will see an error message like below:
image

It suggests the data may become available and it may be a problem if the message doesn't go away.

However, in reality, the data will never appear because the requested data will never be archived. That's because the segment was last edited on say 2022-01-13 08:25:22 meaning we never archive any data from before say 2021-12-13 because of the process_new_segments_from = "editLast30" setting.

Expected:
The message should make it clear why the data won't become available.

This Issue was closed on June 7th 2022
Powered by GitHub Issue Mirror