FMZ FAQ: Logs, Orders, Deployment, Futures, and Indicators

Summary

This FAQ collects practical guidance for operating strategies on the FMZ platform. It explains where runtime logs are stored, notes that the standard order query returns pending orders, and suggests using an exchange’s underlying API when filled-order history is needed and supported. It also outlines deploying a trading Docker on a VPS and keeping it running in the background, while directing users to exchange documentation for API error codes and rate limits.

For futures backtests, the FAQ says to select a contract type before trading, with examples across several exchanges. It also explains that moving-average and other technical indicator outputs can begin with null values because the calculation needs a minimum number of bars. These are platform-specific operational notes, not a trading strategy. The deployment directions and exchange examples may become outdated, and API behavior, symbols, rate limits, and supported contracts should be checked against current provider documentation.

Key ideas

• The standard order query returns pending orders, while filled-order retrieval may require an exchange API.
• A trading Docker can be deployed on a VPS and run in the background.
• Futures backtests may require selecting a contract type before placing trades.
• Indicator outputs can begin with null values until enough historical bars are available.
• Exchange symbols, rate limits, API errors, and contract names require provider-specific checks.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.