We carefully choose our usage of amplify but it serves as a standard event aggregator for our system. One of the advantages of publishing the continuation (w/ the correlation id) through amplify is that we can have multiple subscribers.

An example of another subscriber would be for some of our dialogs that hit the server for information. We can conventionally display a loading state and then transition into the content when it’s available.

I do something similar and use behaviors to issue tokens and track duplicate requests (nonce). I push it through the request headers and listen onbefore and ajaxcomplete, similar to what you did, just not through Amplify.