If vehicle data is missing or delayed, it can affect proactive service, alerts, and your ability to support customers at the right time.
Understanding why this happens helps you quickly identify whether action is needed or whether the behaviour is expected based on the vehicle type, connectivity, or privacy settings.
Common reasons why vehicle data may be missing or delayed
Vehicle data in ConnectedWorkshop can come from different sources. Depending on the vehicle model, connectivity type, and setup, not all data is always available at the same time.
This article covers some of the most common reasons.
1. The vehicle is offline or not currently communicating
If a vehicle has not sent data recently, you may see missing or outdated information.
This can happen when:
- The vehicle has not been driven recently
- Ignition is off
- The CC-Link unit is disconnected or has low power
- Mobile network coverage is limited
You can check the last data received timestamp in the vehicle details to confirm this.
2. Privacy or consent settings limit available data
Some data depends on driver/user consent.
If privacy mode is enabled or consent has not been given:
- Location data may be unavailable
- Trip-related data may be missing
- Some usage data may be limited
This is expected behaviour and not an error.
3. Data source differences (OEM, CC-Link, or both)
Vehicles can be connected through:
- OEM embedded connectivity
- CC-Link hardware
- Both (dual source connectivity)
Not all data types are available from all sources.
For example:
- Warning lights may come from OEM data
- Diagnostic trouble codes may require CC-Link
- Some vehicles rely on a combination of both
If a vehicle has dual source connectivity, data may appear at different times depending on which source provides it.
4. Vehicle model differences (MOD2, MOD3, MOD4)
Data availability also depends on the vehicle generation.
MOD2
No embedded data available CC-Link required for warning lights and diagnostic data
MOD3
Warning lights available via embedded connectivity Diagnostic data requires CC-Link
MOD4 (for example ID.Buzz and new Transporter)
Warning lights available via embedded connectivity Diagnostic data depends on remote diagnosis availability.
Note: Diagnostic data from embedded systems is not available until remote diagnosis is enabled. Because of this, two vehicles of the same model may behave differently depending on how they are used.
5. Recent installation or activation
If a CC-Link unit was installed recently:
- Data may take some time to appear
- The vehicle may still show onboarding or setup-related statuses
This is normal shortly after installation.
6. Temporary platform limitations or ongoing updates
In some cases, data may be missing due to:
- Ongoing system updates
- Temporary integration limitations
- New features still being rolled out
If this affects multiple vehicles, it is usually temporary.
What you should do next
If you notice missing or delayed data:
- Check the Connectivity tab in the vehicle details
- Review the connection status and last data received
- Confirm whether consent or privacy settings apply
Check whether the vehicle requires CC-Link for the data you expect If the issue persists and blocks proactive service, contact support with the vehicle details
Good to know
Missing data does not always mean something is wrong. In many cases, it reflects expected behaviour based on vehicle type, connectivity, or customer settings.
Understanding these differences helps you focus on the vehicles that actually need attention and avoid unnecessary troubleshooting.