Hello!
You can do two things, either using transactionID or setting a retryCount. Like this
Using retryCount
-- Check if RetryCount property exists
DECLARE retryCount INTEGER COALESCE(InputLocalEnvironment.Destination.File.RetryCount, 0);
-- Increment RetryCount
SET retryCount = retryCount + 1;
-- Store the updated RetryCount in LocalEnvironment
SET OutputLocalEnvironment.Destination.File.RetryCount = retryCount;
OR
Setting transactionID
-- Generate a unique transaction ID
DECLARE transactionID CHARACTER;
SET transactionID = UUIDASCHAR;
-- Add the transaction ID to the message as a property
SET OutputRoot.Properties.TransactionID = transactionID;
Regards,
Kjetil Svihus
------------------------------
Kjetil Svihus
------------------------------
Original Message:
Sent: Tue February 09, 2021 07:45 AM
From: Prosanta Saha
Subject: Retry mechanism in ACE v11 with file nodes
Hi,
In the ACE v11 file input node we have a tab for enabling the retry in case of failure with retry threshold and short retry interval.
I have tested the behavior and it works fine, however, each message is treated as a separate transaction. So there is no way to know which one is the original message vs which one is the retry message. I don't see any headers which indicate this retry count.
During processing, is there a way to identify what is the retry count so that the original message vs the retry messages can be linked with a uniqueue Transaction id?
Appreciate help from the experts here.
Regards,
Saha
------------------------------
Prosanta Saha
------------------------------