If other points on the same publisher are working but one specific point is not arriving on the Enterprise side, the most common cause is an XID mismatch introduced when the point was removed and re-added to the publisher. Work through these steps in order:

On MangoES:

• Go to Publishers and open the publisher sending to MangoEnterprise
• Find the entry for the affected data point and note its Published Point XID (this is separate from the data point XID, it typically looks like PP_xxxxxxxx)
• Confirm the data point itself is healthy: add it to a Watch List and verify it is receiving fresh values from the Modbus source
• Confirm the data point's Logging Type is not set to Do Not Log, some publisher configurations will not forward a point that has no logged values

On MangoEnterprise:

• Go to the Data Source that receives published data from MangoES
• Find the data point that is supposed to receive this value and open its configuration
• Look at the Point Locator, it will contain the Published Point XID it is listening for
• Compare this XID to the one you noted on MangoES, if they do not match, this is the cause

To fix:

• Update the Point Locator on the MangoEnterprise data point to match the current Published Point XID from MangoES
• Save the data point, then disable and re-enable the data source on MangoEnterprise to force it to reconnect

If the XIDs already match, also check:

• The data point and its data source are both enabled on MangoEnterprise
• The data type on the Enterprise point matches what MangoES is sending (e.g., both NUMERIC)
• The publisher on MangoES shows a healthy connection status with no errors

The remove/re-add step almost always generates a new Published Point XID on MangoES while the Enterprise side still holds the old one, updating the Point Locator on Enterprise is usually all that is needed