1. In Laravel Telescope’s Job Queries, some SQL statements are not recorded. It shows Queries (22), but there are actually far more than 22. See Figure 1.
2. Checking laravel/telescope in composer.json shows the version is v2.1.7. See Figure 2.
3. After clearing the tables starting with telescope_ and re-running the Job, I found in Laravel Telescope’s Queries that all the SQL statements under Job Queries do exist, but some of them are not linked to the Job. I estimate there are over 1000 SQL statements in the Job, but Laravel Telescope’s Queries only shows 641, so it is still not displaying them all. See Figure 3.
4. Executing the SQL statement, SELECT count(*) FROM `table`.`telescope_entries` WHERE `type` = ‘query’, returns a result of 1375. This indicates that the SQL statements under the Job were fully recorded, just not displayed completely. See Figure 4.
5. Opening an unlinked SQL statement and clicking View Job redirects to the newest Job in Jobs, rather than the Job it should actually be linked to. However, I can confirm based on the Location value that this SQL statement belongs to the Job it should be linked to. See Figure 5.
6. I decided to comment out some unimportant SQL executions in the Job to reduce the number of SQL statements, making it easier to observe the more important ones.