When we design an x-callback-url action, we tend to focus on the x-success parameter because we want to get more things done. Yet, when we use these actions, especially the ones that involve two or more chained actions, sometimes we feel the need to cancel the first task and either return to the original app or continue with the second task. Either way, based on our most frequent use cases, we may need to revisit these chained actions and redesign them to include the x-cancel parameter.
Cancel and Return
For example, in one of my earlier workflows, I share an action that allows you to add an event in Fantastical and a task item in Clear with a single post in Drafts. When I use it on a regular basis, I often find myself cancelling the event and want to return to Drafts. Either because I want to cancel the intent altogether or because there's a major change I need to make on the entire command structure that I prefer to restart it in Drafts. There has never been a case where I want to cancel the event, but continue to add the task item in Clear.