n8n resolves every parameter against its displayOptions when it builds a
Workflow, before any execution exists. A displayOptions on a child of a
collection or fixedCollection made that resolution loop, so image runs
answered HTTP 500 in under a second and left no execution record at all.
Drop those four displayOptions and say in each description when the field
applies, then build the Workflow twice in the validation test - with every
collection present but empty - so this cannot come back.
The action node now speaks the whole TeamoRouter surface instead of a
single prompt: chat messages carry text plus input images (binary or URL)
and can hand the answer to a Chat Trigger as an output field, images can
be generated or edited with the full parameter set (size, quality, n,
output format and compression, background, fidelity, mask) and every
result comes back as binary, as markdown for the chat, or both.
