Change Details

`npm test` and CI to confirm current behavior is not impacted. Using 3.0.0 chronik-client: Create a chronik url array with chronik-native3 during OVH maintenance as the first server and another reachable server as the second server. Attempt a normal tx call. Note that failover proxy does not go to the next server. Using this version: Do the same thing and note a switch occurs, we do get the tx Try the same thing with a bad request i.e. chronik.tx('notatxid') and observe the server does switch over from native-3 but not from the next one in the stack; instead that error is returned

`npm test` and CI to confirm current behavior is not impacted. Using 3.0.0 chronik-client: Create a chronik url array with chronik-native3 during node maintenance as the first server and another reachable server as the second server. Attempt a normal tx call. Note that failover proxy does not go to the next server. Using this version: Do the same thing and note a switch occurs, we do get the tx Try the same thing with a bad request i.e. chronik.tx('notatxid') and observe the server does switch over from native-3 but not from the next one in the stack; instead that error is returned

`npm test` and CI to confirm current behavior is not impacted. Using 3.0.0 chronik-client: Create a chronik url array with chronik-native3 during OVHnode maintenance as the first server and another reachable server as the second server. Attempt a normal tx call. Note that failover proxy does not go to the next server. Using this version: Do the same thing and note a switch occurs, we do get the tx Try the same thing with a bad request i.e. chronik.tx('notatxid') and observe the server does switch over from native-3 but not from the next one in the stack; instead that error is returned