Amazon S3 repo connection failure scenarios

Hi,

I’m having a Amazon S3 repository through which I push a json from my activity to the S3 bucket. This works fine but I need to take care of failure scenarios such as connection to S3 failing due to any reason such as network, timeout, security/auth, etc.

What happens in these scenarios and how Pega handles this and how can I know this failure so I can alert the support group on this issue

When an Amazon S3 connection fails in Pega due to network, timeout, or authentication issues, the activity step that writes to the S3 repository throws a runtime exception and the operation is marked as failed. Pega captures the error details in the step status and the error message is stored in properties like pyStatusMessage and pxError. You can detect this failure by adding proper exception handling in the activity or data flow where the S3 upload is executed. Configure the step to route execution to a failure path when an error occurs. From that failure path, log the error details and trigger an alert such as an email or notification to the support team. This ensures any S3 connectivity issue is immediately visible and actionable.