Symptom: You click "Pull from Scale Tickets," but the Phase Code or Material fields remain blank or show "N/A" on the new ticket.

Solution: Verify that the original scale ticket actually contains a Phase Code and Material. If a scale ticket contains a new Phase Code that FleetWatcher does not recognize, the system is designed to automatically create and map it in the background. If it still fails, the scale ticket data itself may be incomplete.

Symptom: You save a manual shift ticket, hit the browser's "Refresh" or "Back" button, and a duplicate ticket is created.

Solution: The system has been updated to prevent browser refreshes from automatically re-creating tickets. If you still see duplicates, verify you did not accidentally click "Submit Anyway" on the repeat-ticket warning pop-up. Delete the duplicate ticket from the Open summary table.

Symptom: Navigating to the Create Manual Shift Ticket page immediately results in a 500 error or page crash.

Solution: This occasionally happens if the background Key Performance Indicator (KPI) recalculation fails. Capture a screenshot or note the exact time of the error and contact Support.

Symptom: Clicking the Job/Project dropdown crashes the browser with an "Aw Snap" or "STATUS_BREAKPOINT" error.

Solution: This was caused by an older dropdown format struggling with massive project lists. The dropdown has been updated to a searchable format. If this occurs, try updating your Google Chrome browser to the latest version.

Symptom: You run a Preview Export for a large batch of tickets, but the CSV file never downloads and the email never arrives.

Solution: To ensure system stability, FleetWatcher automatically queues and emails CSV exports if you select more than 100 tickets. If the email does not arrive, check your spam folder. As a workaround, limit your selection to 100 tickets or fewer to force a direct download to your browser.

Symptom: Exporting a massive batch of shift tickets to CSV causes the system to time out.

Solution: While export performance has been heavily optimized, it is strongly recommended to keep your Export Batch sizes at or below 2,000 tickets per export.

Symptom: A column like Invoice Number or Employee ID is selected in your export template, but the data is completely blank on the final CSV or PDF.

Solution: First, confirm the data actually exists on the underlying VST. Second, ensure you have not accidentally created a Custom User Defined Field (UDF) with the exact same name (e.g., labeling UDF14 as "Invoice Number"), which causes the system to pull the blank UDF instead of the real system data.

Symptom: You enable "Round Pay to 1/4 Hour" on your template. The Preview Export shows rounded times, but the final exported file does not.

Solution: Ensure you are using the modern Export Batch button, not legacy export pathways. The system has been updated to wire the 1/4 hour rounding logic directly into the final export path.

Symptom: You select "Summary by Job" or another summary option, but the DETAILS section of the generated PDF still shows every single line item.

Solution: The system has been updated to ensure the DETAILS section strictly honors your chosen Summary Option. If you still see full details, verify you did not accidentally leave the Summary dropdown set to "Detail".

Symptom: You attempt to generate shift tickets from a shift, but the loading spinner hangs forever, or only half of the trucks on the shift successfully generate a VST.

Solution: This occurs when a truck's cycle does not satisfy any Zone Analysis Rule in your assigned Rule Set. To fix this:

Symptom: Shift tickets fail to generate entirely because the system doesn't know which rules to use.