# Ignition MQTT Sync Issue

**URL:** <https://forum.inductiveautomation.com/t/ignition-mqtt-sync-issue/83512>\
**Category:** Ignition\
**Created:** [December 26, 2023, 10:16am UTC](https://forum.inductiveautomation.com/t/ignition-mqtt-sync-issue/83512 "2023-12-26T10:16:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![PRASHANTH\_KAKKIRALA](https://avatars.discourse-cdn.com/v4/letter/p/76d3ee/32.png) [@PRASHANTH\_KAKKIRALA](https://forum.inductiveautomation.com/u/PRASHANTH_KAKKIRALA)\
**Post date:** [December 26, 2023, 10:16am UTC](https://forum.inductiveautomation.com/t/ignition-mqtt-sync-issue/83512/1 "2023-12-26T10:16:51Z")

</div>

we are seeing an issue with the MQTT data sync. Here are the details.  
([Set Up Store-and-Forward System | Inductive Automation](https://inductiveautomation.com/resources/video/set-up-storeandforward-system))  
Followed the configuration from this video.

Instantaneous data looks to be good but historical has in issue  
Data on Transmission End:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/c/5ce9c45e01c71783c331d6e129e1b24e81b51d1f.png)  
Data on Receiving End:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/9/19cd19943b7228f9fec209973be7451e030e81b6.png)

what could cause this data difference at subscriber and publisher ends.  
Min/Max aggregation mode is selected. We tried changing this mode to SimpleAverage; the results were slightly better but not identical.  
The system clocks are synchronized.  
Please suggest if there is any configuration to fix this.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 26, 2023, 12:53pm UTC](https://forum.inductiveautomation.com/t/ignition-mqtt-sync-issue/83512/2 "2023-12-26T12:53:57Z")

</div>

Have you tried posting on Cirrus Link's own forum?

> **[Cirrus Link Forum](https://forum.cirrus-link.com/)**
>
> A place to discuss software from Cirrus Link Solutions

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [December 27, 2023, 4:26pm UTC](https://forum.inductiveautomation.com/t/ignition-mqtt-sync-issue/83512/3 "2023-12-27T16:26:14Z")

</div>

The sample frequency is multiple data points per second, so I'm going to go out on limb here and suggest that this discongruity is related to transmission time.

Consider this representation of the data:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/d/7d0f7d2cbf9758720030650ce1b6d96142deccb4.jpeg)

The data actually lines up pretty well, but it is 3 to 5 seconds out of sync.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [December 27, 2023, 9:49pm UTC](https://forum.inductiveautomation.com/t/ignition-mqtt-sync-issue/83512/4 "2023-12-27T21:49:40Z")

</div>

Might look at other topics on here as well: [MQTT Store & Forward](https://forum.inductiveautomation.com/t/mqtt-store-forward/65275)