If a rule with "Chat - Query" cannot connect to the server, it fails silently

I changed from ollama to LM Studio, and the default port for the server changed. I forgot to change this in DT4 (version 4.4) and all my rules with “Chat - Query” actions failed.

The problem is that they failed silently — the query action returned immediately, and the rest of the rule was processed. I couldn’t work out what was going on until I opened the chat pane and repeated the query there; at that point, it displayed “Could not connect to the server”.

Fortunately, the only actions after that were to rename the document based on the chat response (no response, so the renaming was skipped) and to play a sound — but if the documents had then been moved, I would need to find where they’d all gone and bring them back again.

For a chat action, I’d prefer it if failure to connect to the server was an error — it should stop processing, and show the error in the log.

1 Like

Thanks for the feedback, a future release will cancel the rules in case of network issues.