FieldPulse 3.1 is now available to all customers. This release focuses on performance improvements, infrastructure stability, and targeted UI enhancements based on feedback received through support channels and the product portal.

Performance Improvements

  • Dispatch Board Load Time: Initial load time for the dispatch board has been reduced by approximately 40% for accounts with 500+ active work orders. This was achieved through query optimization and the implementation of cursor-based pagination for job lists.
  • Mobile Sync Efficiency: The mobile app now performs incremental syncs more efficiently when reconnecting after offline periods. Data transfer volume during sync operations has been reduced by an estimated 25–30%.
  • Photo Upload Retry Logic: Improved handling of intermittent network conditions during photo uploads. Failed uploads are now queued with exponential backoff and resume automatically when connectivity is restored.

Bug Fixes

  • Resolved an issue where the Work Order Summary Report displayed incorrect totals when date filters spanned fiscal year boundaries. (Related troubleshooting article)
  • Fixed a bug causing the Barcode Scanner to disconnect intermittently on Android 14 devices when using Bluetooth HID mode. (Related troubleshooting article)
  • Corrected time zone handling in the Date Filter on custom reports. Previously, reports using the "Yesterday" preset could return data from two calendar dates depending on the account's configured time zone and the execution time of the report.
  • Addressed a sync conflict scenario where checklist responses edited offline by two technicians would result in data loss for the second submitter.

UI Enhancements

  • The Bulk Actions menu in the work order list now includes keyboard shortcut support. Press Shift + A to select all visible items, Shift + D to deselect.
  • Added a confirmation dialog when navigating away from the Checklist Template Editor with unsaved changes.
  • Improved contrast ratios for status badges in dark mode to meet WCAG 2.1 AA standards.

API Changes

No breaking changes. The /workorders endpoint now returns the estimated_duration_minutes field, which was previously available only through the /scheduling endpoint.

Known Issues

  • Users with custom role permissions may experience a delay of up to 5 minutes before permission changes take effect. A fix is targeted for 3.1.1. (Workaround available)
  • The Map View may exhibit reduced performance when plotting 100+ active jobs simultaneously. We recommend using filtered views or the list-based dispatch board for high-volume operations until this is addressed in 3.2.

As always, the full API documentation is available at developers.fieldpulse.io. For questions about any item in this release, please open a support ticket or post in the Product Feedback forum.

  • Thank you for the documentation flag, Anita. You are correct — the /workorders schema documentation is currently out of sync. Engineering has prioritized the doc update for this week.

    Regarding role permission propagation: There is no API endpoint available for forced cache invalidation at this time. The 3.1.1 patch is currently scheduled for release on July 29, 2025. If your compliance requirements necessitate immediate effect for permission changes, I recommend the following workaround:

    1. Navigate to Settings > Security > Session Management
    2. Select Invalidate Active Sessions for the affected user(s)
    3. Users will be required to re-authenticate, at which point updated permissions are fetched

    This is not ideal for large-scale changes and should be used selectively. I have added your account to the early access list for the 3.1.1 RC build if you wish to validate the fix in staging prior to general availability.

  • Thank you for the detailed release notes. I have confirmed that the API change regarding estimated_duration_minutes is functioning as described in our staging environment.

    It is worth noting that the documentation at developers.fieldpulse.io has not yet been updated to reflect this field's availability in the /workorders endpoint. I have opened ticket DOC-2847 to track this discrepancy.

    Additionally, the 5-minute propagation delay for role permission changes (listed under Known Issues) is not acceptable for our security compliance requirements. Please advise on:

    1. The specific ETA for the 3.1.1 patch
    2. Whether a forced cache invalidation can be triggered via API for critical permission updates
  • Hi Sam! Really glad to hear this is going to make your days smoother out there. We know intermittent connectivity has been a pain point for field teams, and this was one of the top requests we heard from folks like you.

    If you run into any hiccups with the new retry logic once you've had a chance to test it, please don't hesitate to reach out — we want to make sure you're set up for success with these improvements. Feel free to DM me or drop a note here!

  • nice, the photo upload thing was driving me nuts lol. kept failing on job sites with spotty signal