So, this cascading issue is hitting me right now. Being real vague here, in order to support a new capability, we need to insert an asynchronous operation in t

So, this cascading issue is hitting me right now. Being real vague here, in order to support a new capability, we need to insert an asynchronous operation in the middle of what has been a synchronous operation. The synchronous operations is done implicitly and explicitly in many, many places in the app (yes I know this sucks, big old codebases are what they are, and you can only refactor so much at one time while continuing to deliver new features). We have a hard ordering requirement where the new async behavior must be completed before the work can continue. And it's killing us. What would be a simple case of "call this new function" is spiraling into weeks of work and thrown our planning into question. Most of the time it's pretty easy to accommodate the contagion. It's a little more work than is ideal, but it is fine in practice because you hit a natural boundary that stops the spread. But in this case, due partly to tech debt and partly due to deep architectural decisions, it's blocking our ability to move forward in a reasonable amount of time. We will certainly find a solution, but it's going to be much more expensive to get there than it needs to be.