broker_profile_invalid

DataSeen in: Runs

What happened

A run carries a snapshot of the broker profile it was started with. A snapshot that is present but malformed ends that one run with this code, before it reaches the engine, instead of running on a guessed default. The reason is in detail.reason.

What to do

Open the broker profile in Forge settings, check it and save it again, then start the run again.

Example

json
{
  "status": "failed",
  "error": {
    "code": "broker_profile_invalid",
    "message": "The broker profile for this run could not be read.",
    "detail": {}
  }
}

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

Ask about this in the forum