One failed Application Message in an IFS Connect queue (like NOTIFICATION) blocks every other message behind it from processing, while other queues seem to keep processing new messages fine even when failed messages exist in them — what configuration controls this difference?

All FAQ questions / Integrations and APIs

Answer

Check whether the EXECUTE_IN_ORDER checkbox is ticked for that specific queue in the Setup IFS Connect window — a queue with EXECUTE_IN_ORDER checked processes messages strictly in sequence, so a failed message genuinely blocks everything queued behind it until it's cleared, while a queue with it unchecked can skip past a failed message and keep processing others. Also compare the MAX_PROCESSES value between queues — a value greater than 1 (combined with EXECUTE_IN_ORDER unchecked) allows that queue to process multiple messages in parallel rather than strictly one at a time, which is likely why other queues appear more resilient to an individual failed message.

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