Module 7 cheat sheet

ON ERROR CONTINUE
-----------------
handled
scope considered success


ON ERROR PROPAGATE
------------------
handle locally
but remain failed
rethrow upward


TRY
---
localized error boundary


ANY
---
generic catch-all
put specific handlers first


ERROR MAPPING
-------------
connector error
→ APP/domain error


UNTIL SUCCESSFUL
----------------
synchronous retry scope
bounded attempts
MULE:RETRY_EXHAUSTED on exhaustion


RETRY RULE
----------
retry transient failures

don't blindly retry:
bad input
schema errors
permission errors
business validation


TIMEOUT
-------
does NOT prove write failed


IDEMPOTENCY
-----------
required for safe retries


CROSS-SYSTEM WRITES
-------------------
do not assume distributed rollback
design compensation/reconciliation


OBSERVABILITY
-------------
correlation ID
structured logs
no secrets / sensitive payload dumps

If you remember just one sentence from this module, use:

“A timeout is an ambiguous outcome, so I design retries together with idempotency rather than assuming the downstream write failed.”

That's an excellent integration-developer talking point.

Next should be Module 8: Configuration and Security — properties by environment, secure configuration properties, OAuth credentials, External Client Apps/connected-app concepts, TLS, secret management, and how to keep dev/QA/prod Mule deployments identical except for configuration.