Hi Karthikeyan,
I've been retired from IBM now for over a year now and I don't have any recollection of any context variable that would provide this information, but then again my knowledge is getting dated by the day :-) Hopefully an active product developer can provide an answer if anything has been added since I left.
Best Regards,
Steve
------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired
------------------------------
Original Message:
Sent: Wed April 29, 2026 06:56 AM
From: Karthikeyan Narayanasamy
Subject: Identifying connection timeouts on Invoke action
@Steve Linn, Could you please advise if there is any way to achieve this?
------------------------------
Karthikeyan Narayanasamy
Original Message:
Sent: Wed February 18, 2026 04:27 PM
From: Karthikeyan Narayanasamy
Subject: Identifying connection timeouts on Invoke action
Hi Brendon,
I wanted to check if you were able to find a solution for your use case. I'm currently trying to implement something similar and would really appreciate it if you could share any approach or workaround you discovered. Thanks in advance!
------------------------------
Karthikeyan Narayanasamy
Original Message:
Sent: Mon April 07, 2025 11:31 PM
From: Brendon Stephens
Subject: Identifying connection timeouts on Invoke action
Hi
Wondering if is it possible to identify when the backend has had a connection timeout error (ie. processing exceeded the configured timeout settings). It appears this is thrown as a ConnectionError which isn't really granular enough for what I would like. Are there any context variables which may indicate that it was a connection timeout as opposed to something like connection refused?
Thanks,
Brendon
------------------------------
Brendon Stephens
------------------------------