Test, Launch, and Monitor
Once you've built and launched a Wrkflow, learn how to check its results and investigate problems. In this four-minute lesson, you'll follow a space-news newsletter example to trace an unsuccessful API call, add an email notification, test a correction, and review past launches.
What you'll learn
- Inspect a launch in the Debug Console and review each Wrk Action's inputs, outputs, and outcome.
- Use a 404 Not Found response to investigate an API endpoint typo.
- Connect the API Wrk Action's Unsuccessful outcome to a Send email Wrk Action and include its Response body in the notification.
- Launch again to verify that the error notification runs and the message arrives.
- Test the corrected API call with example inputs, then confirm and save the configuration.
- Open the Launches panel to inspect previous runs and their individual jobs.
Make problems visible
If a negative outcome isn't connected, that path through your Wrkflow stops without notifying you. Connect the relevant outcome to a notification Wrk Action when you want an alert. The video handles the API call's Unsuccessful outcome; review other error outcomes separately as you add more Wrk Actions.
A launch marked Completed means execution has ended. Check the individual job outcomes to understand whether each Wrk Action succeeded. Likewise, a successful notification confirms that the alert worked; it doesn't fix the original issue.