In an event-based, distributed architecture, you can't relay on rollbacks to undo actions that have been taken. Instead, you have to actively trigger compensations. This solution is detailed conceptually as the saga pattern. This blueprint demonstrates how to use the BPMN compensation event to implement the saga pattern in a business process that is orchestrated by Camunda. The blueprint also takes advantage of Camunda Connectors for communication via Slack and email. In this example, you can register to adopt a hawk. Communication with the applicant is done via Slack and email, or only email if the person doesn't have a Slack account. If the applicant is rejected, the process throws a compensation event that notifies the applicant that they will not receive a hawk.