A customer workflow calls a slow external API. How would you design the user experience and execution path?

Instruction: Describe the user-facing states and the server execution path together. Explain when asynchronous processing earns its extra operational cost.

Context: Tests whether a slow dependency is handled with clear user expectations, bounded execution and customer operating ownership.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

If the external call regularly exceeds the user's waiting window, I'd use a durable operation record and a worker...

Upgrade to view official answer

Related Questions