CAL_NO_TZ

DataSeen in: RunsCode number 8

What happened

The calendar attached to this run has no time zone Forge can resolve, so its events cannot be lined up with the price data. Before a run starts, the engine settles every setting it depends on, and a setting that cannot be settled ends the run with this code without testing anything. The engine's own text is in detail.reason.

What to do

Upload the calendar again with a time zone set, or pick a different one.

Example

json
{
  "status": "failed",
  "error": {
    "code": "CAL_NO_TZ",
    "message": "The engine refused this run's settings before it started.",
    "detail": {}
  }
}

The reply also carries detail.reason, left out of this sample.

Ask about this in the forum