So ran into something new today after updating to 0.15.3 on all server components. For simplicity, here is a flow run creation in interactive UI:

mutation {
  create_flow_run(
    input: {
      flow_id: "f667e3f3-b5eb-4c52-8f90-36bc54633ac9", 
      parameters: "{\"file_id\": \"42556bd0-f495-11eb-a7a0-8c8590acd4d8\"}"
    }
  ) {
    id
  }
}

Which gives this output. We are getting the same output from our code that runs against graphql endpoint to trigger a flow run and has been working fine for months on 0.14.15.

{
  "errors": [
    {
      "message": "[{'extensions': {'path': '$.variableValues.insert_on_conflict.constraint', 'code': 'validation-failed'}, 'message': 'unexpected value \"ix_flow_run_idempotency_key_unique\" for enum: \\'flow_run_constraint\\''}]",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "create_flow_run"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "exception": {
          "message": "[{'extensions': {'path': '$.variableValues.insert_on_conflict.constraint', 'code': 'validation-failed'}, 'message': 'unexpected value \"ix_flow_run_idempotency_key_unique\" for enum: \\'flow_run_constraint\\''}]"
        }
      }
    }
  ],
  "data": {
    "create_flow_run": null
  }
}

@Marvin archive “Upgrade Database when Using Server on ECS” in server

Hey @Joe McDonald, thanks for the detailed writeup! Glad you figured it out, will keep this reference if I happen to see it again. Just a note though that unfortunately, it is hard for us to support deployments outside of the standard

prefect server start

with docker-compose or using the helm chart.