With the issue that the USGS is having with PDL01, we changed the configuration to allow ShakeMaps to also be sent to PDL02. However, because PDL01 is still down, the ShakeMap code errors out at the PDL submission stage despite being able to send to PDL02. In this case, PDL01 fails but PDL02 succeeds but there is still an error thrown and the code errors out at this stage. For us, this is a problem because it breaks downstream internal processes. Can you please make it so that, in the case there is more than one PDL server in the configuration, it only errors out the code if all fail to connect but only sends a warning when even one of those connections is successful? Thank you.
Please describe your issue here:
With the issue that the USGS is having with PDL01, we changed the configuration to allow ShakeMaps to also be sent to PDL02. However, because PDL01 is still down, the ShakeMap code errors out at the PDL submission stage despite being able to send to PDL02. In this case, PDL01 fails but PDL02 succeeds but there is still an error thrown and the code errors out at this stage. For us, this is a problem because it breaks downstream internal processes. Can you please make it so that, in the case there is more than one PDL server in the configuration, it only errors out the code if all fail to connect but only sends a warning when even one of those connections is successful? Thank you.