Data Sync Edge to Central Gateway

Hi everyone,

I'm experiencing a persistent issue with my Edge Historian synchronization and I'm hoping someone has run into something similar.

Setup:

  • Ignition Gateway (main) connected to an Edge Gateway via GatewayNetwork
  • Edge is configured to forward historian data to the main gateway (remote historian sink)
  • Gateway Network connection between both gateways is confirmed active and healthy

The problem:
I'm seeing the following warning repeating every ~1 minute in my Edge gateway logs:

HistorianSyncable [W]: Remote historian sink isn't accepting data at this time. Likely that the remote gateway is unavailable.

This is happening continuously even though the GAN connection shows as connected on both sides.

What triggered my concern:
My main database had a connectivity issue for about a week. When I went to check if the Edge had captured data during that period as a backup, I found no records for those days either — which suggests the Edge was not successfully buffering or syncing historian data during that entire time.

I also noticed in the Store & Forward logs:

  • RemoteHistorianSink briefly faulted on startup with: "The remote service has reported that it will not accept storage requests to 'CMS_WIS_PROD'"
  • Followed immediately by: "Remote sink service state changed to Available"
  • But the sync warnings continued regardless

What I've already checked:

  • GAN connectivity: both gateways show as connected :white_check_mark:
  • Store & Forward Data Sources on the Edge side
  • Gateway logs on the Edge side

What I haven't been able to confirm yet:

  • Whether the historian sink on the main gateway side is in a faulted state
  • Whether this is a licensing or permission issue on the receiving end

Has anyone experienced this pattern where the GAN is up but the remote historian keeps rejecting data? Any pointers on what to check on the main gateway side would be greatly appreciated.

Thanks in advance!

You should confirm that it is actually fixed. The error sounds like the database connection CMD_WIS_PROD is still broken. Or perhaps is overloaded.