Job System
What it is
Every computation you run on Strateda — whether a single backtest, a parameter optimization, or a walk-forward optimization — is processed as a job. Jobs run in the background on cloud infrastructure, and their results are stored so you can reload them at any time without re-running the computation.
The job system applies to all three computation types:
- Single backtest — one strategy configuration tested against historical data.
- Parameter optimization — a grid search across multiple parameter combinations (e.g., 400 combinations).
- Walk-Forward Optimization (WFO) — rolling in-sample/out-of-sample validation across multiple windows.
How to access it
The job table is located at the bottom of the right panel. It displays your recent jobs and updates automatically as jobs progress.
What you see
Submitting a job
When you click Run (for a backtest) or Run Optimization (for optimization or WFO):
- The platform submits your strategy configuration as a job.
- The job appears in the job table with a running status.
- A progress indicator shows how far along the computation is (0–100%).
- Jobs run one at a time — if you submit multiple jobs, they queue and execute sequentially.
Job completion popup
When a job finishes, a popup notification appears. You have two options:
- Load results — Immediately loads the results into the UI. The chart displays candle data with condition indicators and trade markers; the results panel populates with performance metrics.
- Dismiss — Closes the popup without loading. The results are saved and can be loaded later from the job table.
The job table
The job table shows your most recent jobs with the following columns:
| Column | Description |
|---|---|
| Name | Auto-generated label based on the instrument, timeframe, and direction (e.g., AAPL/H1/buy/#1, AAPL/H1/buy/OPT/#2, ES.FUT/M30/buy/WFO/#1) |
| Status | Current state of the job (see below) |
| Progress | Percentage complete (0–100%) |
| Scheduled | Scheduled execution time, if set (displayed in UTC) |
| Created | When the job was submitted (displayed in UTC) |
| Actions | Available actions depending on the job's status |
Job statuses
| Status | Color | Meaning |
|---|---|---|
| Running | Green | The job is actively processing |
| Pending | Orange | The job is queued and waiting to execute |
| Completed | Blue | The job finished successfully — results are ready to load |
| Failed | Red | The job encountered an error |
| Cancelled | Gray | You manually stopped the job |
Actions
The available actions depend on the job's current status:
- Running jobs — Stop (cancels the job).
- Pending / Cancelled / Failed jobs — Start (restarts the job) or Delete.
- Completed jobs — Delete. Click the row to reload results.
Scheduling jobs
For pending, cancelled, or failed jobs, you can click the Scheduled cell to set a specific execution time. This is useful for queuing jobs to run during off-hours or when your hourly quota resets.
Reloading previous results
Click any completed job row in the table to reload its results into the UI. The platform detects the job type automatically and loads the appropriate view:
- Single backtest — Loads the equity curve, performance metrics, trade log, and chart markers.
- Parameter optimization — Loads all optimization analytics (heatmaps, surface plots, robustness analysis, etc.).
- Walk-Forward Optimization — Loads the full WFO results dashboard with per-window metrics.
You do not need to re-run a computation to view its results again. Any job completed within the last 7 days can be reloaded instantly from the job table — useful for expensive optimization runs with large numbers of parameter combinations.
How to interpret it
Quota and job queuing
Each plan has a limit on how many strategy runs you can execute per hour. If your quota is insufficient when a job is due to run, the platform automatically reschedules it to the next hour when quota resets. You do not need to manually retry — the job will execute as soon as quota is available.
One job at a time
Jobs execute sequentially — one job runs at a time per account. If you submit multiple jobs, they queue in order and execute one after another. This ensures each job gets full computational resources.
Data retention
Job results are stored for 7 days and then automatically purged. All job data — including strategy parameters and results — is encrypted at rest using AES-128 encryption. Your strategy configurations and performance data are never stored in plaintext.
If you need to preserve a strategy configuration beyond 7 days, load the job result and store it as a named strategy — stored strategies are retained permanently until you manually delete them. See Storing & Loading Strategies for details.
Example
A trader runs three jobs in sequence on a Friday afternoon:
- Single backtest on AAPL/H1 with an RSI strategy — completes in under a minute. The popup appears; the trader loads results immediately and reviews the equity curve.
- Parameter optimization with 400 EMA/DEMA combinations on AAPL/H1 — takes several minutes. The trader dismisses the popup and continues other work. The job appears as completed in the job table.
- Walk-Forward Optimization on the same strategy — queues as pending while the optimization runs, then starts automatically when the optimization finishes.
On Monday, the trader returns and clicks the optimization job row in the table. All 400 results reload instantly — heatmaps, surface plots, and rankings — without re-running any computation. The WFO results are also still available for reloading.