BT Mesh Configuration Distributor which the executor belongs to.

Pointer to configuration job which is executed.

BT Mesh stack configuration handle which is returned by the last configuration request (BT Mesh Stack API call). Configuration executor processes those configuration events only which matches this handle.

Current state of the configuration executor.

Identifier of BT Mesh Configuration Executor instance.
The identifier of configuration executor instance shall be unique in the context of parent configuration distributor.

Number of configuration task request retries were executed due to busy BT Mesh Stack. The BT Mesh Stack might reject configuration client requests temporarily due to lack of resources. For example maximum number of parallel segmented message transmissions is reached.
The local refers to the fact that no messages were sent to the configuration server because the BT Mesh Stack did not accept the request.

Maximum number of configuration task request retries were executed due to busy BT Mesh Stack.
The local refers to the fact that no messages were sent to the configuration server because the BT Mesh Stack did not accept the request.

Number of configuration task request retries were executed already due to BT Mesh Stack timeout. An ongoing BT Mesh Stack configuration client request might timeout because the configuration request message sent to the configuration server or the configuration status message sent back to the configuration client is lost. This counter is cleared at the beginning of each configuration task of the configuration job.

Maximum number of configuration task request retries due to BT Mesh Stack timeout which indicates lost configuration messages.

Timer to measure event timeout and configuration request retry interval.

Timer is active from the the moment it is started until it elapses or until it is stopped explicitly.