Petals SE Flowable

Customize the failed job retry

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: No version
  • Fix Version/s: 1.0.0
  • Component/s: Configuration
  • Security Level: Public
  • Description:
    Hide

    Failed jobs are automatically retried.

    The retries can already be configured through the following parameters of the async executor:

    • asyncExecutorNumberOfRetries,
    • asyncExecutorDefaultAsyncJobAcquireWaitTime

    or, at the task level:

    <serviceTask id="failingServiceTask" >
        <extensionElements>
            <flowable:failedJobRetryTimeCycle>R5/PT7M</flowable:failedJobRetryTimeCycle>
        </extensionElements>
    </serviceTask>

    We should be able to set:

    • a default wait time of failed job (ie. when the tasks are executed by an applicative thread and not by the async executor),
    • and, the default wait time of failed async job (ie. when the tasks are executed by the async executor)
    Show
    Failed jobs are automatically retried. The retries can already be configured through the following parameters of the async executor:
    • asyncExecutorNumberOfRetries,
    • asyncExecutorDefaultAsyncJobAcquireWaitTime
    or, at the task level:
    <serviceTask id="failingServiceTask" >
        <extensionElements>
            <flowable:failedJobRetryTimeCycle>R5/PT7M</flowable:failedJobRetryTimeCycle>
        </extensionElements>
    </serviceTask>
    We should be able to set:
    • a default wait time of failed job (ie. when the tasks are executed by an applicative thread and not by the async executor),
    • and, the default wait time of failed async job (ie. when the tasks are executed by the async executor)
  • Environment:
    -

Activity

Christophe DENEUX made changes - Fri, 15 Sep 2017 - 09:46:59 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Christophe DENEUX made changes - Fri, 15 Sep 2017 - 09:47:03 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Fri, 15 Sep 2017 - 09:54:11 +0200
Summary Customize the failed job wait time before retry Customize the failed job retry
Description Failed jobs are automatically retried. We should be able to set the wait time Failed jobs are automatically retried.

The retries can already be configured through the following parameters of the async executor:
* {{asyncExecutorNumberOfRetries}},
* {{asyncExecutorDefaultAsyncJobAcquireWaitTime}}
or, at the task level:
{code}
<serviceTask id="failingServiceTask" >
    <extensionElements>
        <flowable:failedJobRetryTimeCycle>R5/PT7M</flowable:failedJobRetryTimeCycle>
    </extensionElements>
</serviceTask>
{code}

We should be able to set:
* a default wait time,
* and, the wait time at the engine level (ie. when the tasks are executed by an applicative thread and not by the async executor)
Christophe DENEUX made changes - Fri, 15 Sep 2017 - 09:54:22 +0200
Description Failed jobs are automatically retried.

The retries can already be configured through the following parameters of the async executor:
* {{asyncExecutorNumberOfRetries}},
* {{asyncExecutorDefaultAsyncJobAcquireWaitTime}}
or, at the task level:
{code}
<serviceTask id="failingServiceTask" >
    <extensionElements>
        <flowable:failedJobRetryTimeCycle>R5/PT7M</flowable:failedJobRetryTimeCycle>
    </extensionElements>
</serviceTask>
{code}

We should be able to set:
* a default wait time,
* and, the wait time at the engine level (ie. when the tasks are executed by an applicative thread and not by the async executor)
Failed jobs are automatically retried.

The retries can already be configured through the following parameters of the async executor:
* {{asyncExecutorNumberOfRetries}},
* {{asyncExecutorDefaultAsyncJobAcquireWaitTime}}

or, at the task level:
{code}
<serviceTask id="failingServiceTask" >
    <extensionElements>
        <flowable:failedJobRetryTimeCycle>R5/PT7M</flowable:failedJobRetryTimeCycle>
    </extensionElements>
</serviceTask>
{code}

We should be able to set:
* a default wait time,
* and, the wait time at the engine level (ie. when the tasks are executed by an applicative thread and not by the async executor)
Christophe DENEUX made changes - Fri, 15 Sep 2017 - 10:01:32 +0200
Description Failed jobs are automatically retried.

The retries can already be configured through the following parameters of the async executor:
* {{asyncExecutorNumberOfRetries}},
* {{asyncExecutorDefaultAsyncJobAcquireWaitTime}}

or, at the task level:
{code}
<serviceTask id="failingServiceTask" >
    <extensionElements>
        <flowable:failedJobRetryTimeCycle>R5/PT7M</flowable:failedJobRetryTimeCycle>
    </extensionElements>
</serviceTask>
{code}

We should be able to set:
* a default wait time,
* and, the wait time at the engine level (ie. when the tasks are executed by an applicative thread and not by the async executor)
Failed jobs are automatically retried.

The retries can already be configured through the following parameters of the async executor:
* {{asyncExecutorNumberOfRetries}},
* {{asyncExecutorDefaultAsyncJobAcquireWaitTime}}

or, at the task level:
{code}
<serviceTask id="failingServiceTask" >
    <extensionElements>
        <flowable:failedJobRetryTimeCycle>R5/PT7M</flowable:failedJobRetryTimeCycle>
    </extensionElements>
</serviceTask>
{code}

We should be able to set:
* a default wait time of failed job (ie. when the tasks are executed by an applicative thread and not by the async executor),
* and, the default wait time of failed async job (ie. when the tasks are executed by the async executor)
Christophe DENEUX made changes - Fri, 15 Sep 2017 - 10:02:04 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.0.0 [ 10741 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    Fri, 15 Sep 2017 - 09:44:58 +0200
    Updated:
    Fri, 15 Sep 2017 - 10:02:04 +0200
    Resolved:
    Fri, 15 Sep 2017 - 10:02:04 +0200