Unable to Retry transaction for a specific business exception

Help Studio
1

Hi All,

I am using Reframework and 2022 studio version

I have requirement that if any BE occurs with this " ApplePad is Locked for Editing" it should mark that as success and retry that item after three hours. But if second time same error happened it should mark it as failed.

I am able to mark this transaction successful when this error found. Also I am able to add this queue item in orchestrator with all same data. But when it is getting second time this exception it is not able to set transaction failed. I have added one Retry attempt in queue item as well.

But somehow in second attempt it is not able to mark this transaction as failed. Its not retrying after second attempt. But problem is that its is not able to set transaction status failed for second attempt.

Can anyone please help

@sonaliaggarwal47 if you can help with your inputs. Thanks

Regards,
rds

Forum Engagement Daily Reports
2

Hi @rds0511

When this is happening, are you throwing business exception?

Please note that unlike system exceptions which are thrown by system as and when error happens, business exception are the ones configured and thrown by user explicitly.

Wherever this scenario is becoming true, please include throw activity to throw business rule exception with the appropriate error message.

3

thanks for reply. I am able to throw business exception. If you see mentioned issue.

I am able to add that item to queue again when this BE occurs.
But we have requirement, after retry again same BE occurs it should not retry and set status as failed.

Now in my second retry attempt, its not able to set transaction as failed and but good part is that its not retrying again. I will provide error which we are getting in set transaction for retry attempt

1 Like
4

@rds0511

Also check the flow for business exception in set transaction, it should by default do that in re-framework unless you have changed something.

may be re-tracing steps will help identify the root cause here.

how are you marking it as success? first throwing exception, catching and then marking it as nothing?

how are you enabling its retry if it was not marked as failed?

if you can share some screenshots, that would help too.

5

I am catching exception first and if exception matches the keywords, then i am marking this as successful and manually adding to queue for retry. i am using Add Queue item and use another queue element Retry Attempt. So, if retry = 0, then it will catch BE and mark as successful and add queue item for retry. But in second time Retry Attempt will be 1, then if it gets same BE again( same keywords) it will not retry and it should mark it as failed.

Marking as failed in second transaction is not working

6

@rds0511

please show the error you are getting..that would help us understand

cheers

7

@rds0511

have you checked whether the retry count is 1 the second time? I think it is where it is failing as first time you marked it as successful that means it remains as 0 and added another entry yourself so now for that new entry as well, retry would be 0 only initially.

Also are you getting any error or it’s simply marking it as successful second time?

8

Thanks for your reply. In Second retry attempt, its unable to set transaction status as Failed. it should be failed because again same BE occurs. But while setting transaction status, its failed with error that input string was not in a correct format.atSource:retry Set transaction status(Business Exception). So, queue status will be in InProgress for this transaction and it don’t generate report or final output.

9

@rds0511

do you have any retry any where?

can you shoe some picture..

or run in debug mode and check locals panel and see all the variable values used in the activity which is throwing exception

cheers