# \[IGN-15910\]GAN serialization issue with streaming datasets **URL:** \ **Category:** Ignition\ **Created:** [April 7, 2026, 2:55pm UTC](https://forum.inductiveautomation.com/t/ign-15910-gan-serialization-issue-with-streaming-datasets/114958 "2026-04-07T14:55:38Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Rhys\_m](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@Rhys\_m](https://forum.inductiveautomation.com/u/Rhys_m)\ **Post date:** [April 7, 2026, 2:55pm UTC](https://forum.inductiveautomation.com/t/ign-15910-gan-serialization-issue-with-streaming-datasets/114958/1 "2026-04-07T14:55:38Z")
We’ve just run in to similar after updating to 8.3.4. We are returning a dataset from a named query, and then writing that dataset straight to a tag. I suspect it is a similar issue to the one in this thread, but just wanted to make sure it was captured, are you able to confirm this will also be resolved in 8.3.5? ```python Caused by: com.inductiveautomation.ignition.common.model.exception.ProtobufSerializationException: Class 'com.inductiveautomation.ignition.gateway.datasource.BasicStreamingDataset' and object 'Dataset [20R ⅹ 25C]' cannot be Protobuf serialized at com.inductiveautomation.metro.impl.protoserializers.AnyObjectSerializer.toProtobufMessage(AnyObjectSerializer.java:63) at com.inductiveautomation.ignition.gateway.gan.protoserializers.QualifiedValueSerializer.toProtobufMessage(QualifiedValueSerializer.java:37) at com.inductiveautomation.ignition.gateway.gan.protoserializers.QualifiedValueSerializer.toProtobufMessage(QualifiedValueSerializer.java:18) at com.inductiveautomation.metro.impl.protoserializers.ProtobufUtil.packAnyToList(ProtobufUtil.java:190) at com.inductiveautomation.metro.impl.protoserializers.generic.collection.ListSerializer.toProtobufMessage(ListSerializer.java:46) at com.inductiveautomation.metro.impl.protoserializers.generic.collection.ListSerializer.toProtobufMessage(ListSerializer.java:21) at com.inductiveautomation.metro.impl.protoserializers.AnyArgSerializeBuilder.build(AnyArgSerializeBuilder.java:168) at com.inductiveautomation.metro.impl.protoserializers.ServiceInvocationSerializer.toProtobufMessage(ServiceInvocationSerializer.java:41) at com.inductiveautomation.metro.impl.protoserializers.ServiceInvocationSerializer.toProtobufMessage(ServiceInvocationSerializer.java:15) at com.inductiveautomation.metro.impl.protoserializers.ServerMessageSerializer.toProtobufMessage(ServerMessageSerializer.java:47) at com.inductiveautomation.metro.impl.transport.ProtobufDirectAdapter.adaptData(ProtobufDirectAdapter.java:79) at com.inductiveautomation.metro.impl.transport.ProtobufDirectAdapter.adaptData(ProtobufDirectAdapter.java:29) at com.inductiveautomation.metro.impl.transport.AbstractTransportAdapter.handle(AbstractTransportAdapter.java:59) at com.inductiveautomation.metro.impl.MessageSendManager.sendNext(MessageSendManager.java:232) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) ... 3 common frames omitted ``` Managed to resolve bu wrapping the return from the named query in a `system.dataset.toPyDataSet()` ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [April 7, 2026, 3:07pm UTC](https://forum.inductiveautomation.com/t/ign-15910-gan-serialization-issue-with-streaming-datasets/114958/2 "2026-04-07T15:07:43Z")
The [release notes](https://inductiveautomation.com/downloads/releasenotes/8.3.5-rc1) shows a couple of serialization fixes, but I'm not sure if it includes this issue specifically. ---
**Author:** ![Rhys\_m](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@Rhys\_m](https://forum.inductiveautomation.com/u/Rhys_m)\ **Post date:** [April 8, 2026, 1:29pm UTC](https://forum.inductiveautomation.com/t/ign-15910-gan-serialization-issue-with-streaming-datasets/114958/3 "2026-04-08T13:29:42Z")
I’ve just tested 8.3.5 RC1 and the issue is still present there ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [April 8, 2026, 4:32pm UTC](https://forum.inductiveautomation.com/t/ign-15910-gan-serialization-issue-with-streaming-datasets/114958/4 "2026-04-08T16:32:59Z")
Thanks for the report; this is indeed a different issue not yet covered. Serialization across the gateway network is complicated and full of edge cases. ---
**Author:** ![Noah\_Casey](https://avatars.discourse-cdn.com/v4/letter/n/e480ec/32.png) [@Noah\_Casey](https://forum.inductiveautomation.com/u/Noah_Casey)\ **Post date:** [July 1, 2026, 7:06pm UTC](https://forum.inductiveautomation.com/t/ign-15910-gan-serialization-issue-with-streaming-datasets/114958/5 "2026-07-01T19:06:26Z")
Has this been fixed we recently upgraded to 8.3.6 and we are receiving the following error: This is through remote tag providers. ```python ERROR Sender 01Jul2026 15:02:55 Unexpected error while delivering message to the transport layer. com.inductiveautomation.ignition.common.model.exception.ProtobufSerializationException: Class '[Ljava.lang.Object;' and object '[Ljava.lang.Object;@66c49cd8' cannot be Protobuf serialized at com.inductiveautomation.metro.impl.protoserializers.AnyObjectSerializer.toProtobufMessage(AnyObjectSerializer.java:63) at com.inductiveautomation.ignition.gateway.gan.protoserializers.QualifiedValueSerializer.toProtobufMessage(QualifiedValueSerializer.java:37) at com.inductiveautomation.ignition.gateway.gan.protoserializers.SecureSubscriptionUpdateSerializer.toProtobufMessage(SecureSubscriptionUpdateSerializer.java:39) at com.inductiveautomation.ignition.gateway.gan.protoserializers.SecureSubscriptionUpdateSerializer.toProtobufMessage(SecureSubscriptionUpdateSerializer.java:20) at com.inductiveautomation.metro.impl.protoserializers.ServerMessageSerializer.toProtobufMessage(ServerMessageSerializer.java:47) at com.inductiveautomation.metro.impl.transport.ProtobufDirectAdapter.adaptData(ProtobufDirectAdapter.java:79) at com.inductiveautomation.metro.impl.transport.ProtobufDirectAdapter.adaptData(ProtobufDirectAdapter.java:29) at com.inductiveautomation.metro.impl.transport.AbstractTransportAdapter.handle(AbstractTransportAdapter.java:59) at com.inductiveautomation.metro.impl.MessageSendManager.sendNext(MessageSendManager.java:232) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: com.inductiveautomation.metro.api.ex.SerializableNotFoundException: ProtobufSerializable implementation not found for Java class '[Ljava.lang.Object;' at com.inductiveautomation.metro.api.MetroProtobufRegistry.getByJavaClass(MetroProtobufRegistry.java:299) at com.inductiveautomation.metro.impl.protoserializers.ProtobufUtil.getSerializer(ProtobufUtil.java:143) at com.inductiveautomation.metro.impl.protoserializers.AnyObjectSerializer.toProtobufMessage(AnyObjectSerializer.java:60) ... 13 common frames omitted ``` ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [July 1, 2026, 7:11pm UTC](https://forum.inductiveautomation.com/t/ign-15910-gan-serialization-issue-with-streaming-datasets/114958/6 "2026-07-01T19:11:25Z")
The streaming dataset issue in the original post is fixed in 8.3.8. Your stacktrace is different; you should contact support officially so they can determine whether it's something unique (and if it is, get a bug ticket going internally).