Power Platform Community Forum Thread Details

Hi Team,

Problem Description:

We are experiencing significant latency when creating cases in Dynamics 365 through a Power Automate workflow, specifically impacting the ability to immediately retrieve the generated Case ID for our front-end application.

Current Architecture & Process Flow:

Front-End: A web application hosted on AWS serves as our user interface and Backend for UI

Case Creation Trigger (New): Upon submission of a new web form in the AWS application, a process is triggered.

Power Automate Integration: This AWS back-end triggers a Power Automate workflow.

Dynamics 365 Web Request (Existing): The Power Automate workflow, in turn, calls an existing Dynamics 365 Web request (or similar established method, previously used by a Power Apps web form) to create the case within Dynamics 365.

Case Generation & Notification: The case is successfully created in Dynamics 365, and an email notification is sent to the user.

The Core Issue: Latency in Case ID Retrieval

Our critical requirement is to retrieve the newly generated Dynamics 365 Case ID immediately back into our AWS back-end application. This Case ID needs to be stored in our database for future reference and integration purposes, and crucially, displayed to the user on the AWS UI immediately upon submission.

However, we are observing a significant delay:

When the Power Automate workflow triggers the Dynamics 365 Web API request, the entire process, including a child flow, takes approximately 30 to 60 seconds to complete the case creation and return.

Due to this delay, we are unable to display the Case ID instantly on the AWS UI, leading to a poor user experience. Users expect immediate confirmation and the unique identifier for their submitted case.

Specific Questions for Microsoft:

Workflow Optimization Potential:
- What are the recommended strategies and best practices for optimizing Power Automate workflows that trigger Dynamics 365 Web API calls, specifically for case creation, to minimize execution time?
- Are there specific actions or configurations within Power Automate or Dynamics 365 that could reduce the observed 30-60 second latency?

Expected Performance Benchmarks:
- What is the expected or typical latency for a Dynamics 365 case creation via the Web API triggered by Power Automate?
- Is it feasible to achieve a return of the Case ID within a few seconds (e.g., sub-3 seconds, ideally 1-2 seconds), or is the current observed delay considered standard behavior for this type of integration?

Architectural Alternatives for Immediate ID Return:
- If synchronous, low-latency return of the Case ID via the current workflow chain (AWS -> Power Automate -> Dynamics Web API) is inherently limited by platform architecture, what alternative patterns or architectural approaches does Microsoft recommend for immediately providing a newly created Dynamics 365 Case ID back to a calling external system (like our AWS back-end)?
- Are there asynchronous patterns with rapid ID return mechanisms (e.g., using virtual tables, specific real-time APIs, or alternative triggers/actions) that we should explore?
Workflow Diagnostics and Mitigation:
- Can Microsoft support provide assistance in diagnosing the specific bottlenecks within our Power Automate workflow or the Dynamics 365 Web API call that contribute to this delay?
- Is it possible for a Microsoft expert to review our workflow configuration and offer specific mitigation strategies or adjustments?
Goal:

Our primary objective is to enable immediate display of the Dynamics 365 Case ID to our users on the AWS UI upon submission. We require clarification on whether the current latency can be significantly reduced through optimization, or if it represents a default platform behavior that necessitates a different architectural approach for immediate ID retrieval

Categories:

Building flows

@RR-09061056-0 Hi,

If you reply on Power Automate to do so ( create Case ID and return it back immediate), the answer is close to Nope.

Optimization won't make it happen if you want ID immediately (<3s).

My suggestion is ( assume that you use customized Case ID, e.g Case Number) :

Split current flow, async task leave it to power automate ( if the latency is acceptable).
Invoke dataverse API directly from AWS only for the Case ID with a few mandatory info.
Use a custom table to generate the ID, ( async to case table).
create/simulate ID pool ( withdraw ID) in AWS, async with dataverse, so AWS service always has deposit ID on hand.
you have to figure out how to eliminate the ID conflict, for example use different sequence rule for that.

Good luck.