Commands

The Commands resource provides a chronological list of all Artisan commands that have been run by your application. This page helps you track scheduled tasks, queued jobs, maintenance scripts, and any custom console commands, allowing you to identify long-running or problematic executions.

Navigation: Access Commands via the sidebar under the “Commands” section.

---

1. Commands Index Table

• Ordering: Entries are sorted by Started At in descending order (most recent first).
• Pagination: The table displays 50 results at a time. Click Load More at the bottom to append the next 50 entries.

1.1 Columns

1. Command

   • The Artisan command name (for example, cache:clear, queue:work, or any custom command class).

2. Started At

   • Timestamp indicating when the command execution began.

3. Completed At

   • Timestamp indicating when the command execution finished. If the command is still running, this field may be blank or display a placeholder.

4. Duration

   • Total execution time for the command, in milliseconds (or seconds if applicable).

5. View Icon (👁️)

   • Click this icon to open the Command Details view (covered in a separate article).

Note: If a command has not yet completed, the Duration field may show a “—” placeholder until the process finishes and Laritor records the completion time.

---

2. Filters

At the top of the Commands index page, you can refine the list of command executions using the following filter controls:

1. Search

   • Allows you to search by command name or keyword. Partial matches and substrings are supported (e.g., searching “queue” will match both queue:listen and queue:work).

2. Date & Time Range

   • Select a Start Date & Time and End Date & Time to narrow results to command executions that began within that window.

3. Duration

   • A numeric input (in milliseconds) to filter for commands whose total execution time is above or below a specified threshold.

Tip: Combining filters makes it easy to find, for example, all backup:run commands that took longer than 10 seconds during the last 24 hours.

---

3. Load More

• By default, the Commands table shows the 50 most recent executions.
• Click the Load More button at the bottom of the table to retrieve the next batch of 50 entries, ordered by Started At.
• This ensures quick initial load times while still allowing you to paginate through historical command data as needed.

---

4. Best Practices

• Identify Long-Running Commands: Use the Duration filter to surface commands that exceed expected execution times, then click View to inspect details.
• Audit Recent Activity: Sort by Started At to confirm that scheduled or manually triggered commands ran successfully.
• Troubleshoot Failures: If a command did not complete (i.e., Completed At is blank), investigate potential errors or hung processes using the detailed view.
• Spot Irregular Patterns: Combine date-range and search filters to track how frequently or infrequently certain commands run, helping you catch unexpected spikes or gaps.

By leveraging the Commands index table and its filter controls, you can monitor Artisan activity, diagnose problematic executions, and ensure that scheduled tasks and maintenance scripts run smoothly.