Tasks are automatically captured when registered in Laravel’s scheduler in routes/console.php or defined using Schedule::command() and Schedule::call().
Scheduled tasks are one of the primary execution contexts in Nightwatch, alongside requests and commands. Each task execution becomes the starting point of a new trace, where all subsequent events such as database queries and exceptions are captured and linked together to provide a complete picture of your application’s behavior.
Task List
View all scheduled tasks for an application from the Scheduled Tasks panel. Each task is displayed with its name, schedule, next run and execution times, including the average and p95 execution time.
P95 shows the performance experienced by your slowest 5% of scheduled tasks.
It highlights outliers, bottlenecks and inconsistent behavior that average
times hide.
Task Details
Click on any task in the list to view its full details page, which shows the tasks’s performance over time. You can also see every individual execution of a task within it’s parent context. Clicking on an execution opens the full trace, showing the job within the context of its parent lifecycle.
Sampling
There are no direct sampling controls for scheduled tasks. They are always captured.
Filtering
There are no specific filtering methods for scheduled tasks.
Redaction
There are no specific redaction methods for scheduled tasks. However, you may still apply redaction to any of the child events that occur as a result of the scheduled task being executed. For example, you may want to redact the contents of a scheduled task’s output. 