How does Mule 4 handle reconnection and retry strategies?

Mule 4 connectors support automatic reconnection for transient connectivity failures. Two reconnection strategies:

1. Standard Reconnection: Retry a fixed number of times with a configurable frequency (milliseconds between attempts). If all attempts fail, throw MULE:RETRY_EXHAUSTED.
2. Forever Reconnection: Retry indefinitely until connection succeeds. Configured in the connector's connection configuration. For operation-level retry (e.g., HTTP calls that fail with a 5xx): use the Until Successful scope — retries the enclosed processors up to a maximum count with a delay between attempts. Error handling: if Until Successful exhausts retries, it throws MULE:RETRY_EXHAUSTED which can be caught by an On Error handler. Reconnection is distinct from retry: reconnection handles connection-level failures (broken socket); Until Successful handles operational failures (processing errors per request).