IFS Connect's REST sender is configured with accepted_res_codes_ including both 200 and 404, expecting a 404 response to trigger the given failed_callback_fun_ — but the call errors out with 'No output from address line in previous chain link; cannot proceed' instead of invoking that failure callback.

All FAQ questions / Integrations and APIs

Answer

This usually comes down to the failure callback procedure's own signature, not the accepted_res_codes_ configuration itself. The failure callback runs as a background job with a 'Normal Parameter' argument type, which means the procedure must be declared with these exact parameter names: PROCEDURE my_fail_callback(error_text_ IN VARCHAR2, app_message_id_ IN VARCHAR2). If your failure callback procedure doesn't match this exact parameter signature, the framework can't correctly invoke it even though your accepted_res_codes_ and routing are otherwise set up correctly — this specific parameter-naming requirement isn't called out in the standard documentation.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions