I am currently building a UDT to publish via system.cirruslink.transmission.publish() into a custom UNS structure.
In testing I have disabled the broker and on restoring the connection I am getting a large amount of data published at one time. Does this script interface with the default history store and follow the flush parameters as configured? It would be good to maintain a flush period to slowly deplete my buffer and make sure the receiving end has time to process each data point.