Event Trigger - No trigger, fetching invocation info loop

### Version Information

Server Version:
v2.1.0-beta.3, v2.0.10

### Environment

OSS

### What is the expected behaviour?

Event Trigger not triggered even manually on console

### Keywords

event trigger not delivered

### What is the current behaviour?

From console: Loop with the text "fetching invocation info"

No delivered when triggered (if triggered)

### How to reproduce the issue?

Only reproducible in production environment, on my same docker file on local env it's all ok.

### Screenshots or Screencast

### Additional info

Network query response

`
{
"result_type": "TuplesOk",
"result": [
[
"id",
"event_id",
"status",
"request",
"response",
"created_at",
"id",
"schema_name",
"table_name",
"trigger_name",
"payload",
"delivered",
"error",
"tries",
"created_at",
"locked",
"next_retry_at",
"archived"
]
]
}
`

Start by reproducing the event trigger failure in the production environment described in the report and compare it with the working local Docker setup. Inspect the console request that remains on “fetching invocation info” and the returned invocation data shown in the issue. Done means identifying why the trigger is not delivered and confirming the console no longer loops.

Written by the indexing model from the issue text.