Channel Faulting in 1.2.0beta

1

In the 1.2.0beta, we notice that when our provision faults, like in the following example for an undefined value, there are fault messages for all of the channels, rather than just the one the provision is linked to in its preset.

In hindsight, the channel ‘provision’ needs a better name, perhaps ‘provisioning’.

We suspect maybe this is a known issue, so just posting here to confirm this behaviour will likely change in the release candidate.

2019-10-23T18:22:04.192Z [WARN] 10.5.1.203 3c9066-963168_OT142C_B-3c90667da870: Channel has faulted; channel=“default” retries=0 faultCode=“script.ReferenceError” faultMessage=“provError is not defined”
2019-10-23T18:22:04.192Z [WARN] 10.5.1.203 3c9066-963168_OT142C_B-3c90667da870: Channel has faulted; channel=“inform” retries=0 faultCode=“script.ReferenceError” faultMessage=“provError is not defined”
2019-10-23T18:22:04.192Z [WARN] 10.5.1.203 3c9066-963168_OT142C_B-3c90667da870: Channel has faulted; channel=“provision” retries=0 faultCode=“script.ReferenceError” faultMessage=“provError is not defined”
2019-10-23T18:22:04.218Z [WARN] 10.5.1.203 3c9066-963168_OT142C_B-3c90667da870: Channel has faulted; channel=“provision” retries=1 faultCode=“script.ReferenceError” faultMessage=“provError is not defined”

2

This is actually not a bug. Genie combines declarations from all channels into a single profile before applying it. When a fault happens it assumes all active channels failed, then retries them individually and clear the fault if they pass. So although you see 4 fault log entries, you should end up with a single faulty channel at the end of the session.

3

Hello,

Is there any recovery mechanism for any faulted channel.
Let’s say I have a channel named “channelx” associated with a preset “presetx” and provision “provisionx”.
The periodicity of presetx is “2 PERIODIC”.
If the provision script in provisionx fails due to some error (e.g. some coding error
in the provision script), and the error was corrected before next INFORM.

Will provisionx gets triggered during next and subsequent periodic INFORM?

4

Yes, there is a built-in retry and back-off mechanism for faults.

5

Thank you Dan, for the confirmation :slight_smile: