Known anomalies from

FactoryTalk Edge Gateway

standalone version 1.02.00

In some cases, new or updated tags are not shown when the data source is repopulated.To workaround this issue, create a new data source or Clear and populate the existing data source. For both workarounds, to retain current bindings in models, first export the model, perform the workaround, and import the model back in.

Large models might cause the Export window to become unresponsive for some time. There is no workaround for this issue.

After the machine that is running FactoryTalk Edge Gateway restarts, the RSLinxClassic tag is missing from the tag list.To work around this issue:

If running RSLinx Classic as a service, there is no further action needed after a reboot. Data will automatically egress once FTEG and RSlinx service start automatically.
If not running it as a service, if data is not automatically egressing after reboot, the user will need to stop and restart the application.

Importing the data model while the data source is populating, clearing, or deleting results in error or warning messages during import. To work around this issue, wait for the data source to finish populating, clearing, or deleting before importing the data model.

Adding a period in the name of a model or node causes validation errors during import. To work around this issue, remove periods from model and node names.

Azure IoT Hub, or an issue occurring within Azure IoT Hub.To work around this issue:

If the IoT device reached the daily message quota limit, change the Azure subscription to increase the limit.
The device did not reach the message quota limit, but still returns the error, the data egressed successfully to Azure. Select
Acknowledge
in FactoryTalk Edge Gateway to remove the error message.