Prevent Future Backtest Inconsistencies Between Versions (Issue: 142 vs. 143)

Dear SQX Team,

I hope this message finds you well. It has been several years since I began working with your company, and I am writing to share some critical feedback regarding recent platform stability. I trust this input will support your continued development and the long-term sustainability of the community.

I have identified two significant issues that require your attention. First, regarding HTTPS server timeout errors: the interface occasionally indicates that strategy generation is ongoing when the process has actually frozen. I have verified that this is not related to my hardware configuration, as I have meticulously checked all GPU and system settings on my end. I urge you to investigate this discrepancy between the interface status and the actual processing state.

However, the more pressing concern involves fundamental incompatibility between SQX versions 142 and 143. Despite using identical data sets and identical period settings, the backtest engines produce completely divergent results—effectively treating the same strategy as entirely different algorithms. For example, strategies demonstrating excellent performance in version 142 yield catastrophic results in version 143. Upon cross-referencing with MT5 realistic backtesting, version 143 appears to generate accurate results, suggesting the error resides in version 142’s engine.

This issue extends beyond my individual experience. Community posts reveal several other users reporting identical version-specific discrepancies, indicating a systemic problem rather than an isolated configuration error.

Given the irregular release cycle—approximately annual, though occasionally more frequent—I have relied on version 142 as my primary platform for the past year. The prospect of invalidating all portfolios and strategies developed during this period is deeply concerning, as it would render substantial time and capital investment completely meaningless. Therefore, I respectfully urge you to implement rigorous backtest engine validation protocols before finalizing future releases. Consistency across versions is essential for maintaining user trust and protecting the integrity of developed strategies.

Thank you for your attention to these critical matters.

Sincerely,

Hi,

please share more details about your issue with our support at [email protected], we will look into both and help you resolve it