Bug Fixes and Improvements for May 21, 2026

New update for Homeworks, including several bug fixes and improvements:

Bug Fixes

• Mobile (Field Force): Fixed an issue where tapping Clock In/Out or Start/Stop Timer while online could create duplicate time entries, leading to incorrect timesheets and payroll data.
• Employee Management: Fixed an issue where disabling a user's seat did not boot their active login session, so removed users now get logged out and redirected to the login page automatically.
• Communications (SMS): Fixed an issue that completely blocked Australian and UK companies from activating SMS, where the compliance document upload form failed to load and registration attempts hit a dead-end error with no path forward. The compliance form now loads properly with clear guidance for submitting required documents.
• Unscheduled Work: Fixed an issue where visit dates appeared as the year 2001 (about 25 years ago) when adding an item to an existing visit, so users now see the correct visit dates and can select the right one with confidence.
• Dispatch Board: Fixed an issue where opening and closing a visit caused the Budget Hours column to flicker and display the wrong value. Closing a visit with no changes now skips the unnecessary refresh, and success and error messages are consistent across Complete, Skip, Reopen, and Undo Skip actions.
• Invoicing: Fixed an issue where the Crew and Employee filter dropdowns on the Invoices page failed to populate, so users can now reliably filter invoices by crew or employee.
• Invoicing: Fixed an issue where the Processing Fee tooltip and Invoice History dropped trailing zeros in the hundredths place (showing 3.3 instead of 3.30), so processing fee amounts now display with the correct two-decimal currency formatting.
• Routing: Fixed a Dispatch Board crash caused by an infinite loop in the map controller, by removing the legacy route generation code and simplifying map state management so stops render reliably in both light and dark themes.
• Schedule: Fixed an issue where single (non-recurring) events could disappear from the calendar and Dispatch Board because of how the recurring-event flag was evaluated, so single events now always appear as expected.
• Customers: Fixed an issue where deleting an event, recurring event, or property left orphaned tag records behind, so tags are now properly cleaned up when these items are deleted.
• Mobile (Field Force): Fixed an issue on visit detail pages where the wrong user's running timer could be shown when multiple employees were clocked in, and where skipping a visit while a timer was running could leave the timer orphaned. Timers are now correctly scoped to the current user, and skipping a visit cleanly stops any running timers.
• Payments (Stripe): Fixed background errors and white-screen failures when a connected Stripe account's permissions were revoked. The system now detects the bad connection, skips affected background sync jobs, and shows clear warnings on the Customer page, Stripe Settings page, and as a global banner so the issue can be resolved.

Improvements

• Dispatch Board: When two or more visits are selected in the Move Visits flow, the "Move all future events for recurring/multi-step events" checkbox is now hidden, so users can no longer trigger unreliable bulk updates across multiple recurring series. The option still appears when only one visit is selected.
• Customers: Backfilled historical emails with their correct customer association and removed unreliable legacy email matching, so the customer communications page loads faster and shows the right correspondence on each customer's timeline.
• Schedule: Added new filters to the events list for whether a visit is invoiced or recurring, and whether it has any running timers or any tracked time, so the upcoming events table can be sliced more precisely.
• Customers: When a customer's email, name, phone, or address is updated, those changes now sync to the connected Stripe contact and to past email correspondence, addresses are re-geocoded for accurate map placement, and phone numbers are stored with the proper country code. New customers also respect the company's configured starting customer number and payment-method-required policy.

Have feedback or questions? Contact our support team.