Failed to Extract

Tried several versions of both Revit and Speckle Revit Plugin (including the new beta 3.0) and keep producing this error during serialization and upload:

2024-09-18 08:40:55.468 -07:00 [ERR] SendCommand failed - Failed to extract (pre-serialize) properties from the Speckle.Core.Models.Collection
Speckle.Core.Serialisation.SpeckleSerializeException: Failed to extract (pre-serialize) properties from the Speckle.Core.Models.Collection —> System.OperationCanceledException: The operation was canceled.
at System.Threading.CancellationToken.ThrowOperationCanceledException()
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeObject(Object obj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeBasePropertyValue(Object baseValue, PropertyAttributeInfo detachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeBase(Base baseObj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeObject(Object obj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeBasePropertyValue(Object baseValue, PropertyAttributeInfo detachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeBase(Base baseObj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeObject(Object obj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeObject(Object obj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeBasePropertyValue(Object baseValue, PropertyAttributeInfo detachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeBase(Base baseObj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeObject(Object obj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeObject(Object obj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeBasePropertyValue(Object baseValue, PropertyAttributeInfo detachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.PreserializeBase(Base baseObj, Boolean computeClosures, PropertyAttributeInfo inheritedDetachInfo)
at Speckle.Core.Serialisation.BaseObjectSerializerV2.Serialize(Base baseObj)
— End of inner exception stack trace —
at Speckle.Core.Serialisation.BaseObjectSerializerV2.Serialize(Base baseObj)
at Speckle.Core.Api.Operations.d__29.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Speckle.ConnectorRevit.UI.ConnectorBindingsRevit.d__128.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at DesktopUI2.ViewModels.StreamViewModel.d__214.MoveNext()

Hi @jpdalbora ,

Thanks a lot for the report, could you please upload this file in the folder I just shared with you?
We’ll need to debug this to see what’s going on.
Also, what version of Revit are you on?

1 Like

Hey @teocomi - I have uploaded the file. It is Revit 2022.1 - Thank you.

Hey @jpdalbora ,

Thanks for sharing the file. I’ve opened the file by detaching from central and tried sending via Next-Gen connectors. It seems to be working on my end. Can you try following the same steps and try sending via next-gen connectors (3.0 beta)?

image

image

It seems this family is throwing the errors. We’ll look into fixing it.

3 Likes