we reproduced on Cloud this wasn't displayed after creating a segment.
This may be a regression in core?
There was another issue about this notification in case of empty report (because no data, not because not processed), but impossible to find it again... 🤔
Let's make sure we add UI tests once this is resolved so we can catch if it regresses again
I'm actually not able to reproduce that problem locally. When browser archiving is disabled and I create a new segment the notification is shown. And there is a UI test for exact this case:
The only change around that logic I could find is https://github.com/matomo-org/matomo/pull/18540
I can't reproduce this locally as well. Will try again today.
@mattab are you still able to reproduce this issue and provide info about the steps?
@justinvelluppillai it can be reproduced on Cloud (in our instance), but i haven't reproduced on on-premise yet, but you had maybe reproduced it before? or maybe it's just an issue on Cloud
fyi reproduced today again on Cloud, created a random segment and there was no notification box:
Because the issue is only happening on Cloud, we will close it here, and Cloud team will investigate.
reproduced on demo2
Relevant config values that are e.g. used on demo2:
browser_archiving_disabled_enforce = 1 enable_create_realtime_segments = 0 enable_browser_archiving_triggering = 0 process_new_segments_from = "last60"
I can recreate this on locally and on demo2 by creating a new segment which will not return any visits for the selected time period.
This is because of the code 'if no visits recorded, data will not appear, so don't show the message'
This is intentional behavior added as part of #12823, but it's potentially confusing as experienced users wouldn't expect a new segment to be 'ready' immediately and seems a bit inconsistent that the segment will sometimes show as unprocessed depending on the selected period.
@mattab Do you have any preferences on how to proceed with this?
I'd go with 1) to make things consistent & simple, maybe?
Closing due to complications to implement and not being worth it yet