Recent Bug Fixes

• Asking AI Insights to compare the next four weeks against the last four weeks returned a per-week average that was too low. Skimmer now calculates and displays the correct per-week average for that comparison.
• When AI Insights searched for a specific product or text term, it built the search in a way that didn't follow Skimmer's standard method for handling user-provided text. Skimmer now uses that standard method for these searches.
• AI Insights sometimes returned incorrect profit figures when a question spanned a date range that had to be split into multiple periods. Skimmer now calculates profit correctly across split date periods every time.
• When AI Insights answered a profit question, the header sometimes displayed the wrong date range for the answer. Skimmer now shows the correct date range on profit answers.
• AI Insights occasionally showed a technician's route assignment start date instead of the actual service date when listing daily route stops. Skimmer now consistently shows the correct service date for each route stop.
• AI Insights displayed route-stop times in UTC instead of local time, putting them five hours off from Service History. Skimmer now displays route-stop times in local time in AI Insights Reports, matching Service History.
• AI Insights treated scheduled, completed, and skipped service stops inconsistently, which could produce misleading counts. Skimmer now applies consistent logic across scheduled, completed, and skipped stops.
• Asking AI Insights for a sales total could return very different numbers depending on whether it counted invoiced amounts or actual payments collected, sometimes even showing opposite year-over-year trends for the same question. Skimmer now applies one consistent, clearly defined sales total so results are reliable no matter how the question is phrased.

Note: These issues only affected pros signed up for the Embedded Bookkeeping Beta.

• When Layer calculated sales tax on an invoice, rounding each line item separately could push the total a few cents above the tax total shown on the Skimmer invoice. Skimmer now calculates Layer's sales tax so it matches the invoice's tax total exactly.
• When enrolling a batch of accounts in Layer, a single failed item could stop the whole batch without reporting the failure or retrying it. Skimmer now isolates failures so one problem account no longer stops the rest of the batch from enrolling.
• A customer's payment was recorded, but the matching account credit was never applied, leaving the account balance incorrect. Skimmer now applies the account credit correctly whenever a payment is recorded.
• A data export crashed whenever a customer activity log entry was missing an update timestamp. Skimmer now handles missing timestamps gracefully so the export completes successfully.

• AI Insights built its underlying queries with incorrect start and end date values. Skimmer now generates the correct dates.
• Start and complete times for route stops in AI Insights tables displayed in UTC rather than the user's local timezone. Skimmer now shows these times in local time.
• When a pro asked AI Insights a question about a specific day of the week, like "how many stops did I do on the last Monday of each month,” the answer reflected the wrong day. Skimmer now rejects an invalid weekday calculation instead of quietly correcting it to the wrong day, so "last weekday" questions return the day that was asked about.
• Because service dates were stored with a time component, questions about a specific day (like "last Monday") returned zero matching results. Skimmer now matches on the date correctly, regardless of the stored time.
• Questions about installed items pulled results from a customer tag with a similar name instead of actual installed-item records, returning payment data instead of item data. Skimmer now pulls from the correct installed-items data.
• Filters like "stops after 3pm" compared against UTC time while the results displayed in local time, so the wrong stops came back. Skimmer now compares filters in local time so the results match what's shown.
• AI Insights displayed a placeholder date of January 1, 2010 as the completion time for service stops that hadn't finished yet. Skimmer now leaves the completion time blank for stops that aren't done.
• Questions about time spent on work orders pulled from an empty data source and always returned zero. Skimmer now pulls from the correct source and returns accurate durations.

• Some customers' invoices appeared correctly in the Pool Service tab but not in the Invoices Preview section. We corrected the display logic so invoices now appear consistently in both locations.

• The AI Insights column detector missed several money columns and incorrectly flagged some count columns as currency fields. We updated the detection algorithm to recognize additional money column patterns and reduce false positives.

• When asking for data about a specific date, AI Insights sometimes ignored that date and returned results for a broader default range instead. AI Insights now respects the date specified when the data table is built.
• In the expanded view of the AI Insights panel, the data table would jitter while text was typed in the prompt field. The layout no longer jitters when you type in the prompt field.
• When an AI Insights query returned no matching data, an empty table was rendered instead of a clear no results message. The view now displays a no results message instead of an empty table.

• When you searched by customer name in the Quotes or Invoices pages and then deleted the text from the search field, the filter was not cleared and the results list stayed filtered instead of resetting. These lists now refresh when the search field is emptied.

• When importing products from a spreadsheet, any row with a markup percentage above 999.99 or an oversized cost or price value caused the entire import to fail with only a generic "Failed to import" message. The importer now validates those fields before saving and returns a clear message explaining which value is out of range.
• When importing customers from a spreadsheet that included a Customer Status column, that column was ignored. Every imported customer was set to Lead, regardless of the value specified in the spreadsheet. The import now reads and applies the status value from the spreadsheet correctly.

• The selection fields for reminder days and suspension days in Invoicing Settings didn't respond to taps on Safari for iPhone and iPad, making it impossible to update those settings on mobile. The fields are now fully usable on iOS Safari.

• Admin users could not approve quotes on behalf of customers, even when payment was not required at the time of approval. Admins can now approve quotes without a credit card being required. 

• When a work order was linked to a customer registered as a business rather than an individual, the customer name displayed as "null null" instead of the company name. Company names now appear correctly on work orders.
• When work orders on a job were moved to Scheduled, the parent job's status did not update and stayed stuck at "Not Started." The job status now recalculates correctly when work orders are scheduled.