You're on call for Zen Electron's order confirmation Connector, the one you built in this module. The incident queue holds a mix of reports from developers, the marketing team, and customers. In several of them, two causes produce the same symptom. Your job is to find the single check or decision that separates them.
Before you answer, write down for each scenario the first thing you would check and what result would confirm each cause. Then compare your notes with the feedback.
Learning path complete
You have completed the Deploy and build Connectors module and the Integrate with commercetools learning path. You can now decide whether a requirement needs an integration, assign a source of truth to each data domain, and select a connection point with a stated contract for latency, failure behavior, idempotency, and ordering. You can choose where an integration runs and adopt it at the lowest viable step. You can also start a Connector from an official template, publish it privately, install it in the correct Region and environment, and diagnose a Deployment when it misbehaves.
Together, these decisions form an integration approach: plan the landscape first, then build and operate each integration against its contract.
Before Zen Electron uses the Connector in production, the email guide's Verify and operate the integration section lists the provider, inbox, and failure tests that a real provider adds.
To apply the same approach to Zen Electron's other flows, return to the landscape plan from Plan your integration landscape. For each row, follow the guide listed in Use the integration guides, and use the
commercetools-connect skill for the build steps that this module taught. The guides cover other application types, such as service and job applications, that this module didn't exercise.