You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today should respect Timezone in the transitions report
Current Behavior
When looking at Transitions reporting, I am getting Exception NoDataForAction. I am running this report for today as the time period.
Earlier (today), however, transitions was reporting data.
If I select the report for a wider date-range (but still inclusive of today), I get the data/report again.
My timezone is set as US New York for the site (and also in general settings).
It is currently still the Oct. 21 here, but UTC has flipped to Oct. 22. See logging below.
My thought is that the query “today” is not respecting Timezone and trying to pull data for Oct. 22 - a day that has not happened yet (where I live :slight_smile: ) Any thoughts on this as the problem? Any fix or config I can try? Thanks!
Debug log is showing (a few representative entries): ERROR API[2021-10-22 00:52:46 UTC] [0e58b] Uncaught exception in API: /var/www/…/plugins/Transitions/API.php(195): NoDataForAction Uncaught exception in API: /…/plugins/Transitions/API.php?date=today&actionType=url&actionName=https%3A%2F%2Fmysite.com%2F&expanded=1&format=JSON&module=API&method=Transitions.getTransitionsForAction&filter_limit=-1&idSite=2&period=day, CLI mode: 0]
This might indeed be a problem around midnight maybe. Haven't tested that through but I think the API uses UTC timezone to create the period. Maybe that needs to be done in the site's timezone here:
sgiehl
added
Bug
For errors / faults / flaws.
and removed
Potential Bug
Something that might be a bug, but can't be reproduced (yet).
labels
Nov 13, 2022
Expected Behavior
Today should respect Timezone in the transitions report
Current Behavior
Possible Solution
No idea
Context
From: https://forum.matomo.org/t/transitions-report-exception-nodataforaction-timezone-issue/43533
Your Environment
The text was updated successfully, but these errors were encountered: