<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Why a strategy gets filtered and the  status is success?]]></title><description><![CDATA[<p dir="auto"><img src="/community/assets/uploads/files/1755017240518-filtered.png" alt="filtered.png" class="img-responsive img-markdown" /></p>
]]></description><link>http://quantiacs.com/community/topic/709/why-a-strategy-gets-filtered-and-the-status-is-success</link><generator>RSS for Node</generator><lastBuildDate>Mon, 10 Aug 2026 14:11:16 GMT</lastBuildDate><atom:link href="http://quantiacs.com/community/topic/709.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 12 Aug 2025 16:47:30 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Why a strategy gets filtered and the  status is success? on Wed, 20 Aug 2025 09:26:30 GMT]]></title><description><![CDATA[<p dir="auto">Dear <a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/372">@gjhernandezp</a>,</p>
<p dir="auto">That strategy is filtered out because it exceeds limits (memory or time) that a strategy has. Your strategy is using machine learning, so that is risky section and could lead to something like this. The success status is irrelevant, it is probably some edge case. The only thing that matters is the status of the strategy which is filtered.</p>
<p dir="auto">Best regards</p>
]]></description><link>http://quantiacs.com/community/post/2006</link><guid isPermaLink="true">http://quantiacs.com/community/post/2006</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Wed, 20 Aug 2025 09:26:30 GMT</pubDate></item></channel></rss>