Known Issue: Missing Data After Mobile+ Migration from Loads 1.0 to 2.0 for Drivers
Use this KB article to troubleshoot potential known issues in the new 2026 Transflo User Workflow features (also known as Loads 2.0).
The new Load Overview screen data and labels for certain load data on this screen might have changed or simply been moved higher or lower on the screen. Use the following workarounds to scroll up or down to find the data. The load data might not be missing. The load information might simply have changed location on the screen.
In the new load user workflows, a Scan button appears only when it is needed in the current step of the load workflow. It is not necessarily missing. The Scan button will re-appear when the driver needs to scan or upload a document to complete the current step in the load.
As a driver, complete each step in the load workflow. If the step requires document scanning, a Scan button will appear. It is not missing. It's placement on the screen has dynamically changed to guide drivers when scanning is needed.
-
Tap Back to exit the Loads feature.
-
In the main menu or dashboard, tap Scan Documents.
-
It is also possible to show or hide a persistent Scan button at the top of the new load screens. Instead of appearing only when needed in the current step, drivers will always see the Scan button.
-
As a fleet administrator, contact Transflo to advise them if you prefer to show or hide the persistent Scan button for your drivers instead of just showing the Scan option only if the current step needs it.
The configuration option name is disableStopScanButton and it has a Boolean value of Yes (disable/hide) or No (enable/show).
Workaround: Drivers might need to scroll down to find the trip number. It is not missing. It's placement on the screen has changed.
For this known issue, users might see the following error message in the steps of a new load workflow:
Trip Number [or other <Field Name>] must use alphabetical characters only.
Users cannot tap Submit. The field should accept numeric digits; however, the known issue does not accept the numeric data.
Workaround: None at this time.
This condition requires a rollback to Loads 1.0 until the workflow configuration field-level validation can be fixed in the new load workflow designer portal to support numeric digits in the Trip Number or similar field.
Note: Minor known issues in the user interface, although inconvenient for some drivers, are not major bugs. The data and features are typically still available. The load data or button location might have moved. If you believe an important feature or data you previously had with Loads 1.0 is no longer available after your migration to the new Loads 2.0, try to apply one of the listed workarounds.
If you cannot find the data or button and believe it is blocking you from performing your job, escalate to your supervisor or fleet administrator. They can work with Transflo to resolve the issue in a configuration fix or future update. Only in the most severe cases, if warranted, your fleet leadership can request a temporary rollback from Loads 2.0 to 1.0 again. In 2026, the legacy load features will be discontinued and all fleets will eventually be migrated successfully to the new load workflow features.


