Bug Fixes for Version 1.78

This article lists the bugs fixed in Version 1.78, plus a few additional Version 1.77 fixes that shipped after that release went out.

Definition

This article refers to different sections of the application. You can consult their definitions below:

Bug Fixes Included in This Release

Self-Serve Portal

• Dashboard Respects Restricted View. A self-serve user with the Orders Restricted View permission could see orders, addresses, and counts belonging to other users on their account from the dashboard. The dashboard now applies the same restriction as the order list.

Dispatch Board

• Status Icon On Grouped Orders. Dispatching an order from a grouped Autodispatch suggestion didn't update its status icon on the board. The icon now refreshes correctly.

Batch Transactions

• Entry Amount Reverting To $0. A race condition between concurrent requests could revert an already-recorded batch transaction entry's amount back to $0. Corrected.
• Posting Blocked By Zero-Amount Invoices. A batch transaction couldn't be posted when the account had invoices with no amount, even though the batch and reference totals matched. Corrected.

Tenant API

• CreateRouteContainer Body Support. The CreateRouteContainer endpoint only accepted parameters in the query string; it now also accepts a POST body, while still supporting the query string for existing integrations.

Checkpoints

• Changing A Used Checkpoint To Driver. Changing a Checkpoint already used on a Route Checkpoint to type Driver crashed the Route Checkpoint grid. This change is now blocked with a validation message instead.

Analytic Views

• Layout Broke With Many Filters Selected. Selecting several filters on a view could push the Execute button off-screen and make results unreadable. Layout now adjusts correctly regardless of filter count.

Extra Fees

• Case-Sensitive IDs Allowed Duplicates. An extra fee type could be created with the same ID as an existing one using different letter casing, silently overriding it. Extra fee IDs are now treated as case-insensitive.

Accounts & Transactions

• Long Attachment File Names Overlapping. A long attachment file name could overlap surrounding text on the transaction attachment list. Fixed.

Service Levels

• Delivery To Date Off By One Day. When an order's Ready At fell on a day off before the service level's booking cutoff, the calculated Delivery To date was one day early. Corrected.

Order Rules

• View-Only Permission Returned An Error. Users with view-only permission on order rules got a 401 error instead of read-only access. They can now view order rules in read-only mode as expected.

Fuel Surcharges

• Scripted Rate Not Recalculating Automatically. A scripted fuel surcharge rate wasn't automatically recalculated when the triggering charge was added or removed from an order. Recalculation now applies automatically instead of requiring a manual API call.

Scripts

• Script Editor Pane Not Anchored. The script editor pane didn't anchor to the bottom of its container when expanded, leaving extra white space below the code. Corrected.

Bug Fixes Included in Version 1.77 After Release

Billing & Payments

• Duplicate Charges On Retry. An automated billing run that hit a transient error while charging invoices could retry and charge already-processed invoices a second time. Charges now include a unique key so retries can't duplicate a payment.
• Duplicate Payment Submission. Paying an invoice by credit card could intermittently send two identical requests from a single click, causing the second to fail and the transaction to display as failed even when the payment succeeded. Duplicate submission is now prevented.

Grid & Dispatch Board

• Panels Not Closing On Drag And Drop. On Next Gen grid boards, the Order Details panel and the driver sliding panel no longer closed automatically when dragging and dropping an order, as they did on legacy boards. Restored.
• Empty Cells Not Following Sort Direction. Sorting a column left empty cells pinned to the bottom regardless of sort direction. Empty cells now follow the sort direction as they did on legacy grids.
• "Is Late Or At Risk" Filter. Orders that had entered At Risk status weren't returned by the "Is late or at risk" filter, and were incorrectly matched by "Is not late and not at risk" instead. Corrected.

AutoDispatch

• Committed Workload Blocking New Orders. AutoDispatch pinned a driver's entire existing workload ahead of any new suggestion, so an order that could have been inserted into a gap in the driver's day was instead withheld indefinitely. AutoDispatch can now insert an urgent, serviceable order into a driver's available time instead of only appending after all committed work.

Chat

• Unread-Message Indicator Overloading The Database. The unread-message indicator (chat red dot) checked the database far more often than needed, and at high volume this degraded performance tenant-wide. The check is now lightweight and no longer scales with the number of participants in a channel.

Route Optimization

• Route Creation Failing On Return Orders. Creating a route could fail when a return order referenced an original order that had already been delivered and was no longer in the route file. Route creation no longer fails in this case.

Driver Settlements

• Settlement Generation Silently Failing. Generating a driver settlement could silently fail with no settlement created and no error shown, caused by a crash when an order item was removed and re-added with the same ID. Fixed.

Tenant & Customer API

• Quote With Invalid Service Level. Creating a quote with an invalid or unknown service level ID returned a generic error instead of a clear validation message, and could return the wrong price or place an unwanted credit hold. The endpoint now returns a specific validation error and no longer preauthorizes the card.
• Driver Attributes Added Via API. Attributes added to a driver through the API didn't appear on the dispatch board until the driver's attributes were re-saved through the UI, which triggers the needed sync.
• Fuel Surcharge Missing Distance. Distance-based fuel surcharge rules could evaluate as false because the pricing payload didn't include the order's distance. Distance is now included so surcharges calculate correctly.

Self-Serve Portal

• Orders Grid Missing Scrollbar. The Self-Serve orders grid had no scrollbar and no maximum width, letting content run to the edge of the screen. Horizontal scrolling and a max width have been added.
• Contact URL Not Erroring Out. A contact URL with a valid but mismatched account number loaded silently instead of returning a 404, the same as an invalid account ID.

Pricing & Fuel Surcharges

• Pricing Zone Not Refreshing. Changing an order's addresses didn't refresh its pricing zones or prompt for a re-price, leaving stale zone data on the order.
• Fuel Surcharge Schedule Updates Ignored. Updates to a fuel surcharge schedule weren't reflected when recalculating fuel surcharge on existing orders, even though the new values were saved correctly.

Extra Fees

• System Extra Fees In Wrong Language. System-generated extra fee names and units of measure could keep displaying in the tenant's original language after its primary/secondary language settings were changed. These auto-generated fee names, along with system exception codes and default billing cycle descriptions, now update automatically when a tenant's language settings change.

Invoicing & Reports

• Large Invoices Failing To Download. Large invoice documents could fail to download, and every retry re-generated the report from scratch and timed out the same way. Invoice rendering now runs asynchronously and caches the result, so large invoices generate reliably.

Attachments

• Invoice Attachments Missing File Extension. Invoice PDF attachments were sent without a file extension. Fixed.
• Driver App Photo Stuck Uploading. A driver app photo attachment could get stuck retrying its upload indefinitely instead of stopping after repeated failures.

Order Cancellation & Editing

• Segments Not Cancelled With Parent. Cancelling a multi-segment order didn't always cancel its individual segments when segment creation and cancellation happened in close succession.
• Attributes Tab Cancel Button. Clicking Cancel on the order Attributes tab after checking or unchecking boxes visually applied the changes instead of discarding them.

Address Book

• Address Suggestion Not Triggering. The address suggestion feature didn't trigger when entering a postal/zip code while adding a new contact address under Settings, even though it worked when creating an order.

Order List Filters

• Contains / Does Not Contain Totals. Combining a "contains" and "does not contain" filter on the same field didn't return counts that added up to the full order total.

Routes Page

• Routes Page Redirecting To Fulfillment. Navigating directly to the Routes page could silently redirect to the Fulfillment/Orders page after a background re-authentication, since the return URL wasn't preserved.

Performance

• Azure Search Slowdown. Enabling the Order Views feature caused a spike in Azure Search response times and request throttling for all customers. The feature was temporarily disabled while the underlying load issue was resolved.