Thread Errors & Solutions

All Thread Blocks have specific configuration requirements in order for them to run properly. Thread Errors can occur at configuration time, during a reload or during a real-time execution. It is important to address any Thread errors that occur to ensure your Threads are working as expected. Large amounts of errors can cause performance issues across all Threads on the organization, therefore, even if you are just testing out a configuration, it is important to address any errors or de-activate the Thread before leaving the Thread Builder.

Error Details

Logic Block

Due to the flexibility of the Logic Block, there are a significant amount of errors that can occur if your Logic is not configured correctly. All Logic Block errors and solutions can be found here.

No Translation Found

This is a common Thread Error for many Thread Blocks on Class Threads. "No Translation Found" errors occur when a Thread Block on an Instance Thread cannot find the Translation for a specific Property on the Instance Twin. In order to fix this error, Users should first verify the Instance Thread should be able to find the Translation (details on how Thread Translation works can be found here). If the Property connected to the Block falls within the specific Translation rules, then this error can be fixed by Reapplying the Class to the Twin and re-activating the Thread. Be sure to check the Instance Translation Table to verify everything looks good.

This error automatically deactivates Threads, be sure re-activate all Instances after the issue has been fixed. Reapplying the Class will not re-activate Threads that were deactivated due to errors.

Inputs or Outputs not Configured

This error occurs when a Thread Block is missing an Input or Output Property. Check to make sure the Block has all required Inputs/Outputs.

This error automatically deactivates Threads. If this error is occurring on a Class Thread, be sure re-activate all Instances after the issue has been fixed. Reapplying the Class will not re-activate Threads that were deactivated due to errors.

Configuration Missing EventType

This error occurs on Blocks that require Events when an Event Type is not configured on the Block. Add the correct Event Type to the Block and re-run the Thread.

This error automatically deactivates Threads. If this error is occurring on a Class Thread, be sure re-activate all Instances after the issue has been fixed. Reapplying the Class will not re-activate Threads that were deactivated due to errors.

No Properties Matching Criteria

This error occurs when a Thread Block cannot find active Properties that match what is configured on the Thread, or the Properties on the Twin do not have any data.

Thread Not Found in Cache

This error typically indicates that the Thread was run too soon after it became Active. Try running the Thread again in a few seconds or de-activate, save and re-activate the Thread.

Master Block Not Found in Cache

This error indicates that a Class Thread was published that has an extra block not connected to the Thread Path, check the class Thread, remove any unconnected blocks and republish the Thread.

Block Not Found

This error occurs when a Block is not directed to a proper property (such as an output property on a Class that wasn't related), or the Class was removed from the Instance Twin. Make sure the Outputs are pointed to the property property, republish the Thread and reapply the Class.

A Value for Comparison Must be Defined

This error occurs when a Thread block, such as the If Logic Block, requires a value to compare in order to execute. Make sure all fields in the Block are configured correctly for the comparison expected.

ReadDataParms Returned Null Property Info

This error occurs when a Thread Block is expecting a Property in the parameters configured in the Block or a PropertyID in the document being passed into the Thread Block but it is not there. Documents being passed into Blocks will overwrite Block configuration, so be sure the correct Parameters are being passed in.

This error automatically deactivates Threads. If this error is occurring on a Class Thread, be sure re-activate all Instances after the issue has been fixed. Reapplying the Class will not re-activate Threads that were deactivated due to errors.

ReadDataParms Returned Null Time Range

This error occurs when a Block is expecting both a start and end time and the document being passed in does not contain both a start and an end time.

This error automatically deactivates Threads. If this error is occurring on a Class Thread, be sure re-activate all Instances after the issue has been fixed. Reapplying the Class will not re-activate Threads that were deactivated due to errors.

Positive Duration Expected

The error: "value ('00:00:00') must be greater than '00:00:00'" occurs when a Thread Block is expecting a time range or a positive duration and it is being passed '00:00:00'. Be sure to verify the Document going into the Block has a duration that is larger than 0.