Bruno Murino

07/17/2021, 9:17 AM
Hi everyone, I’m deploy some of my flows via ECS Service with 1 container that registers the flow and starts a local agent. Problem is that no exceptions are thrown on the service, however the flows are stuck on “scheduled” and never run and my hasura container is throwing this error:
  "type": "http-log",
  "timestamp": "2021-07-17T08:43:42.608+0000",
  "level": "error",
  "detail": {
    "operation": {
      "user_vars": {
        "x-hasura-role": "admin"
      "error": {
        "path": "$.selectionSet.insert_project.args.objects",
        "error": "Uniqueness violation. duplicate key value violates unique constraint \"project_tenant_id_name_key\"",
        "code": "constraint-violation"
      "request_id": "c8aedf52-53fc-4e54-9149-a1d62db270f0",
      "response_size": 193,
      "query": {
        "variables": {
          "insert_objects": [
              "tenant_id": "712db680-3e15-469d-b6e7-eee61a60593d",
              "name": "Health Monitoring",
              "description": null
        "query": "mutation($insert_objects: [project_insert_input!]!) {\n    insert: insert_project(objects: $insert_objects) {\n        returning {\n            id\n        }\n    }\n}"
    "http_info": {
      "status": 400,
      "http_version": "HTTP/1.1",
      "url": "/v1alpha1/graphql",
      "ip": "",
      "method": "POST",
      "content_encoding": null

Kevin Kho

07/19/2021, 5:00 AM
Does your service both register the flow and start an agent? How many flows are being run?

Bruno Murino

07/19/2021, 9:13 AM
yes! Just 1 or 2 flows — Odd thing is that I deploy identically to 2 different aws accounts, UAT and PROD, and it’s working fine on UAT but not on PROD — I keep checking the localAgent logs and they never “receive” the request to run the flow on PROD…, but on Prefect UI I can see the agent is indeed querying for runs every few seconds
so my understanding is that the localAgent can communicate with the server, and also that both the flow and the agent have the same labels (auto-generated), so I can’t see why it doesn’t work
@Kevin Kho I bumped all containers of prefect server to version 0.15.1 (they were on the “fixed” version of 0.15.0 as per that issue I had with schedules not showing), and it seems to have fixed the problem on PROD