- Loading "Upkhand Adhikari" court data is resulting in a "The operation has timed out" error due to its extensive dataset. Surprisingly, similar errors are appearing for courts like Tehsildar, Nayab Tehsildar, and others, despite their smaller datasets.
- The report for "Sambhagaya Ayukt" court, which contains 990, 1351, and 1258 records, is opening without issues, as shown in the detailed court-wise summary report in the provided screenshot.
- Analysis of the query performance reveals significant differences between the production and staging environments. The query takes 16 seconds in production and 8 seconds in staging, as evidenced by the accompanying screenshots. Despite optimization efforts and the use of numerous aggregate functions in calculations, the query performance remains suboptimal.
- Following discussions with the Axpert support team, we examined the "DBTimetaken" and "Timetaken" columns in the axpertlog table. The values in the database are in six digits, whereas Kumar sir suggests they ideally should be in three digits.
Note: Similar reports that were in use from long time is now throwing the same error "The operation has timed out"
In summary, this issue is critical, as these reports are heavily used by thousands of users daily, and the client has raised concerns multiple times. Please advise on the necessary steps to address this issue.
