Well I don't know if you are asking about awaiting two requests at once or how the next.js server handles them but you can do something like this:

import { Post } from "~/src/components/post"

import { getUser } from "~/src/app/actions/user"
import { getPosts } from "~/src/app/actions/post"

export async function HomePage() {
  // this runs the requests in parallel unlike code below
  const [user, posts ] = await Promise.all([getUser(), getPosts()]);

  // below code does not run in parallel and would be slower
  /*
    const user = await getUser()
    const posts = await getPosts()
  */

  return (
    <main>
      <div>{user.username}</div>
      <div>
        {
          posts.map((post) => <Post post={post} />)
        }
      </div>
    </main>
  )
}

Yes, I know you can do that. I mean, running 2 server actions from the client in parallel, no from a server component

If this was a client component it still wouldn't allow you to parallelize server actions using Promise.all or Promise.allSettled. It's a technical restriction at the moment that server actions run in sequence no matter how you call them. Also, Promise.all does run concurrently on Node, not in parallel.

This is the closest I can get, and it works

I wonder if the react team plans to make running them in a non-sequential order?

I don’t think this is a React limitation, I believe it’s rather a Next.js limitation, according to what the [React docs say](https://react.dev/reference/rsc/use-server#caveats):

Accordingly, frameworks implementing Server Functions typically process one action at a time and do not have a way to cache the return value.

They talk about “frameworks implementating” them, not React itself being the issue.

How come 'server actions are just api routes but closer to the developer', but then 'not parallel unlike api routes'

I didn't know each framework was responsible of the server action implementation. I thought it was something that came already built in react. Good to know, thanks

Don't be rude and ping random mods.