# Retry configuration is not maintained

**URL:** <https://forum.flowable.org/t/retry-configuration-is-not-maintained/3660>\
**Category:** Flowable Engine\
**Created:** [April 2, 2019, 4:49am UTC](https://forum.flowable.org/t/retry-configuration-is-not-maintained/3660 "2019-04-02T04:49:35Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sukalpo](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/sukalpo/32/1143_2.png) [@sukalpo](https://forum.flowable.org/u/sukalpo)\
**Post date:** [April 2, 2019, 6:29am UTC](https://forum.flowable.org/t/retry-configuration-is-not-maintained/3660/3 "2019-04-02T06:29:50Z")

</div>

Hi @filiphr , Thanks for the reply.

I am sharing the xml below. The extension that I am telling about is to add the flowable:failedJobRetryTimeCycle that is in the xml.

Also attaching the Java Delegate. So the main objective is to throw a runtime exception. And when the retry count reaches a threshold to throw a BPMNError. I am expecting the boundary error event will catch this event and then process will flow to the LogErrorTask which is also not happening. Thanks in advance.

```
public class GetClaimablePoliciesTask implements JavaDelegate {
public static int retry = 0;
private static final Logger LOG = LoggerFactory.getLogger(GetClaimablePoliciesTask.class);
@Override
public void execute(DelegateExecution delegateExecution) {
    retry++;
    LOG.info("Retry count:- " + retry);
    if (retry != 4) {
        throw new RetryableException();
    } else {
        throw new BpmnError("mail");
    }
}

```

}

## XML

[BPMN XML](https://pastebin.com/embed_js/fBMRr66f)

---

_[View the full topic](https://forum.flowable.org/t/retry-configuration-is-not-maintained/3660)._