Document Failure Scenarios/behaviors

[uchennakevinm1]

What happens to our message delivery and ordering guarantees during various failure scenarios.

Fixed number of failure scenarios:

1. Upstream resource failure
2. Connector Failure / Error - Bug in the connector code. Something about not typical operating behavior.
3. Conduit
4. Transforms
5. Downstream Connector
6. Downstream Resource

Make each one of these steps fail and then write down what the developer can expect.

Resist the urge to fix bad behaviors. We’ll prioritize that work appropriately.

At a minimum get the list of places where we need to test.