Agent Login History Report – Empty CSV Output

[Hem]

Hello everyone,

We’re currently running Version 20.0 Update 7 (Build 1019 Beta) of 3CX, and we've encountered an issue with the Agent Login History report.

Our users have reported that the CSV file generated by the scheduled report (set to "Yesterday") is consistently empty, despite agents being active during that time. This report is scheduled to run daily.



Upon investigating, we discovered a related issue when manually generating the report via the 3CX Admin Console:

• When selecting a custom time period for a single day (e.g., 10 October), the report output is also empty—matching the CSV file our users receive.
• We also tested using a time range of 12:00 AM to 11:59 PM, but the result remained the same.

Interestingly, when we select a two-day range (10–11 October), the report returns correct data—but only for 10 October.



This behavior suggests a possible issue with how data is being presented or retrieved for single-day ranges. Has anyone else experienced something similar? Are there any known workarounds or fixes?

On further investigation we discovered that most likely all queues have the same issue.

Looking forward to your insights.

Best regards,
Hem

 

[AndreasPo_3CX]

Hi @Hem

Can you show us a screenshot when you set the filter like the screenshot below?

 

[Hem]

Hello,

The first screenshot shows the filter and output configuration that fails to produce results. The report is set to a single-day range—specifically, October 10.



The second screenshot displays a filter configuration that successfully retrieves data, but it only returns results for October 10th.

 

[AndreasPo_3CX]

Hi @Hem

You are right, it seems to be an issue with custom range filter.
If you need to use a custom filter use whole days (i.e 10/10 00:00 - 12/10 00:00 which should show 10/10 and 11/10)

Thank you for reporting this, it will be fixed in Update 8.

 

[Hem]

Hello Andreas,

I’d like to highlight that the issue also appears to affect pre-defined filters. As mentioned earlier, our users receive a scheduled report with the range set to "Yesterday", but the output consistently contains no data. Could you kindly verify this behavior for all pre-defined ranges as well?



Additionally, I have a question regarding the custom time period setting:
If I configure the report for a range such as 10–11 October and schedule it to run daily, will the report dynamically update to reflect 11–12, 12–13, and so on? Or will it continue to generate the same report for 10–11 October each day?

When update 8 is expected?

Thank you for your time and for your efforts in resolving this issue.

Best regards,
Hem

 

[AndreasPo_3CX]

Hi @Hem

Regarding scheduled reports with custom ranges, they will not roll the date as you mentioned. If you schedule a report for 10-11 October, it will show data for that date every time it generates.

Regarding the predefined ranges like "Yesterday" we have tried it again on our side and we dont have the issue you are mentioning.
I will send you a PM to get more details on it.

 

[AshishKushwaha]

Hello @Hem If you are looking to generate reports based on status and queue, we have a solution for you.


We’ve developed an advanced reporting system that provides detailed insights on calls, agents, and more. The system includes 3CX agent login tracking—both by queue and by status.


For example, when an agent changes their status to “Away,” the system captures data such as when the status was changed and how long the agent remained away.


Please find the screenshots below for your reference. Let us know if you’d like to schedule a demo of the application.

Email: [email protected]

 

[Hem]

Hi @Hem

Regarding scheduled reports with custom ranges, they will not roll the date as you mentioned. If you schedule a report for 10-11 October, it will show data for that date every time it generates.

Regarding the predefined ranges like "Yesterday" we have tried it again on our side and we dont have the issue you are mentioning.
I will send you a PM to get more details on it.

We tested again and the issue is not with the predefined ranges only for the custom range filter.