Runtime Error: thinkscript.runtime.TooComplexException

[Thayanidhi]

Hi All,

I am completely new to Think script platform, I am trying to learn and creating custom code but i am getting the below error when i tried to add multiple conditions.

com.devexperts.tos.thinkscript.runtime.TooComplexException: The complexity of the expression suggests that it may not be reliable with real-time data.

Is there any limitations in think script or am i missed anything in my code?

Regards,
Thaya

 

[JabronLames]

Hi Thaya,

I'm new here, but maybe I can help. Are you able to link the study you are attempting to run?

***In my experience a long series if 'IF statements' can cause this in TOS. Also, if you're attempting to convert a study to a watchlist column, make sure to take out unnecessary code that pertains to the chart.

 

[BenTen]

The error says it all. The script you're working on may be too complicated for certain tasks (ex: using a scanner with it). Post the script or the exact feature that you're using.

 

[Thayanidhi]

Thanks for a quick reply..
Yes, I am getting error when i tried to add thinkscript label in my watch list coloumn.
Is there any limitetations in watchlist coloumn?

 

[JabronLames]

Of course there are limitations, but no one is privy to exactly what those limitations are...

 

[Thayanidhi]

The error says it all. The script you're working on may be too complicated for certain tasks (ex: using a scanner with it). Post the script or the exact feature that you're using.

Thanks Ben Ten, Yes, We are using some scanner in that scripts and try to get values from scanners. The script with scanner is working if we need to get 1 or 2 value but if we need to get multiple values then we are getting the runtime or complex exceptions.

 

[GimmickFace]

Unfortunately there are some scans that are too complex for TOS, so you get that error. It happens when I try to turn some of my complex studies into scans. Nothing you can do about it unfortunately.

 

[darkejo]

Does anyone have any more information on this error message? I see some that have answered replied with "The error says it all..." but unfortunately it doesn't. I can preview a study-based conditional order just fine after saving a conditional order, but after a couple previews using the same symbol and same code, I then begin to get this error message. To circumvent this, I don't preview the study-based order on the same stock more than once and the trigger works just fine. There is more to this error message than meets the eye.....

 

[MerryDay]

Does anyone have any more information on this error message? I see some that have answered replied with "The error says it all..." but unfortunately it doesn't. I can preview a study-based conditional order just fine after saving a conditional order, but after a couple previews using the same symbol and same code, I then begin to get this error message. To circumvent this, I don't preview the study-based order on the same stock more than once and the trigger works just fine. There is more to this error message than meets the eye.....

https://usethinkscript.com/threads/answers-to-commonly-asked-questions.6006/#post-57834

 

[darkejo]

Unfortunately your post does not answer my question, it just illustrates why I'm asking it.

I understand the workarounds and the "best practices" to use to try and avoid the the topic in question, but when the workaround or best practices no longer work (Ex: Code cannot be shortened any further in length or process, etc..), I figured I'd ask if anyone found an actual way to use more complex scripts than TOS allows by default, or found an actual workaround that solves my issue. It doesn't matter now, though; I found a way to bypass that message regardless of length or complexity -- a bug, but a welcomed one for once. If I had known all the limitations and secrets TOS has, when I first started, I would have moved to tradestation a long time ago.

On a different note.... Thank you for putting that forum together. It was very helpful when I first started playing with thinkScript. I originally tried posting this message in your forum but you no longer allow replies.

JD