Resolving the Issue of Async Await in Node.js: Understanding Simultaneous Execution

---

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Async await in node- 2 simultaneous awaits not getting executed

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---

However, even seasoned developers can run into problems. One common issue arises when trying to execute two asynchronous operations simultaneously using await. Let's take a look at a specific example that many developers encounter.

In the given scenario, a user noticed that only the first await call was functioning properly, and the second await was not. When the first await was commented out, the second would work perfectly. This led to confusion about what was going wrong. The paths specified were correct, and the files were confirmed to be non-empty.

Analyzing the Solution: Fixing the Async Await Execution

After closely examining the code, the root cause was identified to be a small but critical mistake in the implementation of the Promise. Let’s break down the solution into clear and organized sections for a better understanding.

The Key Mistake

The way the Promise was structured in the getText function was incorrect:

[[See Video to Reveal this Text or Code Snippet]]

The parameters are named incorrectly which can lead to confusing outcomes. The correct structure should be:

[[See Video to Reveal this Text or Code Snippet]]

Understanding Promise Resolution and Rejection

In JavaScript, a Promise can either be fulfilled (resolved) or rejected. The order of the parameters in the promise constructor defines how the values are handled:

Resolve: When the operation is completed successfully.

Reject: When there is an error.

The mistake in the parameter order meant that when resolve(data) was called, it actually triggered the rejection due to the naming confusion, leading to an undesired result where only errors were logged.

Correcting the Code

With the correct order of parameters, your getText function will look like this:

[[See Video to Reveal this Text or Code Snippet]]

Complete Code Example

Here's the fixed version of the code that demonstrates proper use of async await with simultaneous executions:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By correcting the parameter order in the promise constructor from (reject, resolve) to (resolve, reject), the await calls in your asynchronous function will work as intended. This change will allow you to execute multiple asynchronous operations simultaneously, maintaining clarity and effectiveness in your code.