"Fast" Reports and the report.fastThreshold
I realise more context is needed here:
- All position data exists, this is confirmed
- Replays for all dates are possible, there are no issues here
- I can trigger the problem by running a custom Trip report for, say 7:16am on one day to 7:16am the next day, which runs. If I run a report for 7:16am to 7:17am, it will not run.
As a result, if I try to run a Trip report for "This Week" or "Previous Week" or "This Month" or "Previous Month", I get nothing for the weekly reports. For the "this month" report I get data up to the 2nd of October. For "last month" I get everything (because this is before we upgraded to 6.9).
I'm pretty sure 6.9 had some issues. Why not the latest version?
We did not notice issues until yesterday, and we have limited windows where we push updates. That's basically the reason, but we will schedule a 6.10 update out of window due to the notification from customers.
In the interim, what is the difference between a "Fast" and "Slow" report. I cannot find a definition of it here on the site.
Fast reports use events and slow reports use raw positions.
In advance of upgrading from 6.9 to 6.10, changing the value of report.fastThreshold to 40-days worth (3456000) has solved the issue. Why 40? Well I just added a few days beyond 31 in case someone wanted a report a bit longer than a month.
Now at least, users can run reports like "this month" for their trip reports. It's almost like the default value setting was always supposed to work this way but didn't take effect until 6.9?
Not sure I understand the question. It always worked.
OK, so our business updated to v6.9 on the 2nd of October. Customers have notified us that reports run in the browser for anything more than 24 hours (we assume caused by report.fastThreshold) just don't run. Or more to the point, they will produce data up to the day that we upgraded to Traccar 6.9 (2nd of October).
I get that we probably need to change this threshold, but: