Using external data source object as a trigger execute the search going on into infinity and delivers no results

[MarkusHeld]

Used Zammad Version

6.3.0-1713882094.d1107375.bullseye

Environment

Installation method: any
Operating system (if you're unsure: cat /etc/os-release ): any
Database + version: any
Elasticsearch version: any
Browser + version: MS Edge v.120.0.2210.121 (64-Bit)

Actual behaviour

If I select an object with type "External data source field" in a trigger as an action, then it finds nothing here and searches for an eternity.

Object:

Trigger:

Similar to this Issue:
#5006

Expected behaviour

When using an object "external data source" in the action for a trigger, i can also search for entries in the "external data source" and get results as a dropdown menu like in the ticket itself to select the wanted entry.

Steps to reproduce the behaviour

1. Create an object field for an external data source.
2. Try to create a Trigger with the object field created in 1) as an action. When entering the desired search term, no tickets are found, but the external data source seems to continue searching.

Support Ticket

Ticket#10154217

I'm sure this is a bug and no feature request or a general question.

yes

[Irisita]

One additional information:
This issue is not only affecting triggers. It's also happening for Macros, Schedulers, Reporting Profiles.