FTRACK processor looping

General
, ,
1

hello everyone, we’ve got a problem on the ftrack processor and we are failing to debug it. basically it’s looping through this event constantly:

{
  "id": "e29c7da451d411f0b2697e6d332bb560",
  "hash": "5060ae91a053195e2bc35618525743e2f076115ace77302fa8b12932680611d7",
  "topic": "ftrack.proc",
  "sender": "processor-1.4.4-prod",
  "senderType": "ftrack",
  "project": null,
  "user": "service_ash",
  "dependsOn": "30c9ac2a519611f0a5145604f545aba0",
  "status": "finished",
  "retries": 0,
  "description": "Processed Event processing",
  "summary": {},
  "payload": {},
  "createdAt": "2025-06-25T15:58:41.045749+01:00",
  "updatedAt": "2025-06-25T15:58:42.551470+01:00"
}

Because of the loop some of the function are now unavailable (like Prepare project action and so on) and the id in there does not correspond to any event in our ftrack instance (of course seeing that its is an ayon id)

do you have any inkling on how to get to the bottom of this?

2

looking better at the actual context for events, it looks like it’s a different id everytime, only the 51d411f0b2697e6d332bb560 in the id is the same. Same goes for the dependsOn, which is different but the tail end is the same 11f0a5145604f545aba0. Problem is, these events keep going on (i got one every 1-2 secs) and i don’t know how to stop it. Maybe there’s a malformed event that gets picked up from the leecher? but the leecher is only leeching healthchecks from ftrack, no other log from there. basically the processor is stuck processing infinitely.

3

Screenshot 2025-06-25 171134
Screenshot 2025-06-25 171134874×984 132 KB

this is basically the state of our event server now