Concurrent submissions handling in Remix

Introduction

Concurrent submissions handling helps your app manage multiple form submissions at the same time without errors or data loss.

When users might click the submit button multiple times quickly.

When multiple users submit the same form simultaneously.

When you want to prevent duplicate data entries in your database.

When you want to show loading states or disable buttons during submission.

When you want to handle race conditions in form processing.

Syntax

Remix

export async function action({ request }) {
  const formData = await request.formData();
  // process form data here
  return redirect('/success');
}

// In the component
const transition = useTransition();
const isSubmitting = transition.state === 'submitting';

The action function handles form submissions on the server side.

The useTransition hook tracks the submission state in the UI.

Examples

Basic server-side form submission handler that processes data and redirects.

Remix

export async function action({ request }) {
  const formData = await request.formData();
  const name = formData.get('name');
  // Save name to database
  return redirect('/thank-you');
}

Disables the submit button and shows a loading label while the form is submitting.

Remix

import { useTransition } from '@remix-run/react';

export default function ContactForm() {
  const transition = useTransition();
  const isSubmitting = transition.state === 'submitting';

  return (
    <form method="post">
      <input name="email" type="email" required />
      <button type="submit" disabled={isSubmitting}>
        {isSubmitting ? 'Sending...' : 'Send'}
      </button>
    </form>
  );
}

Handles concurrent submissions by checking for duplicates before saving.

Remix

export async function action({ request }) {
  const formData = await request.formData();
  const email = formData.get('email');

  // Check if email already exists to avoid duplicates
  const exists = await checkEmailExists(email);
  if (exists) {
    return json({ error: 'Email already registered' }, { status: 400 });
  }

  await saveEmail(email);
  return redirect('/welcome');
}

Sample Program

This example prevents duplicate email submissions by storing emails in a Set. The submit button disables during submission to avoid multiple clicks. If the email is already registered, it shows an error message.

Remix

import { json, redirect } from '@remix-run/node';
import { useTransition, Form } from '@remix-run/react';

let emails = new Set();

export async function action({ request }) {
  const formData = await request.formData();
  const email = formData.get('email');

  if (emails.has(email)) {
    return json({ error: 'Email already registered' }, { status: 400 });
  }

  emails.add(email);
  return redirect('/thank-you');
}

export default function NewsletterForm() {
  const transition = useTransition();
  const isSubmitting = transition.state === 'submitting';
  const error = transition.type === 'actionReload' && transition.submission ? transition.submission.formData.get('error') : null;

  return (
    <Form method="post" aria-label="Newsletter signup form">
      <label htmlFor="email">Email:</label>
      <input id="email" name="email" type="email" required aria-required="true" />
      <button type="submit" disabled={isSubmitting} aria-busy={isSubmitting}>
        {isSubmitting ? 'Submitting...' : 'Subscribe'}
      </button>
      {error && <p role="alert" style={{ color: 'red' }}>{error}</p>}
    </Form>
  );
}

Important Notes

Use useTransition to track submission state and disable inputs to prevent double submissions.

Always validate and check for duplicates on the server side to handle concurrent users.

Show clear feedback to users during and after submission for better experience.

Summary

Concurrent submissions handling prevents duplicate or conflicting form data.

Use server-side checks and client-side UI states together.

Disabling buttons and showing loading states improves user experience.

Practice

1. What is the main purpose of handling concurrent submissions in a Remix app?

easy

A. To prevent users from submitting the same form multiple times accidentally

B. To speed up the server response time

C. To allow multiple users to submit the form simultaneously without any checks

D. To disable all form inputs permanently after one submission

Solution

1. Step 1: Understand concurrent submissions

   Concurrent submissions happen when a user submits a form multiple times quickly, causing duplicate or conflicting data.

2. Step 2: Identify the purpose of handling them

   Handling concurrent submissions prevents these duplicates by disabling the submit button or checking server-side if a submission is already in progress.

3. Final Answer:

   To prevent users from submitting the same form multiple times accidentally -> Option A

4. Quick Check:

   Concurrent submissions handling = prevent duplicates [OK]

Hint: Concurrent submissions handling stops repeated form sends [OK]

Common Mistakes:

• Thinking it speeds up server response
• Assuming it allows all submissions without checks
• Believing it disables inputs forever

2. Which of the following is the correct way to disable a submit button during form submission in Remix using React hooks?

easy

A. Submit

B. Submit

C. Submit

D. Submit

Solution

1. Step 1: Understand disabling with state

   In Remix, you track submission state with a variable like isSubmitting to disable the button only during submission.

2. Step 2: Choose the correct syntax

   Using disabled={isSubmitting} disables the button dynamically, unlike hardcoded true or false.

3. Final Answer:

   <button disabled={isSubmitting}>Submit</button> -> Option A

4. Quick Check:

   Dynamic disable uses state variable [OK]

Hint: Use state variable to disable button dynamically [OK]

Common Mistakes:

• Hardcoding disabled to true disables button always
• Using wrong state variable name
• Not disabling button at all

3. Given this Remix action function snippet handling form submissions, what will happen if two submissions occur almost simultaneously?

export const action = async ({ request }) => {
  const formData = await request.formData();
  const email = formData.get('email');
  if (await isEmailRegistered(email)) {
    return json({ error: 'Email already registered' }, { status: 400 });
  }
  await registerEmail(email);
  return json({ success: true });
};

medium

A. The server throws a syntax error

B. Both submissions succeed, possibly creating duplicate registrations

C. The second submission fails if the first completes before it checks

D. The form disables automatically on the client side

Solution

1. Step 1: Analyze server-side check

   The function checks if the email is registered before registering it, preventing duplicates if the first finishes first.

2. Step 2: Understand race condition handling

   If two submissions come close, the second will fail if the first completes and registers the email before the second checks.

3. Final Answer:

   The second submission fails if the first completes before it checks -> Option C

4. Quick Check:

   Server check prevents duplicates by failing second submission [OK]

Hint: Server checks prevent duplicates if first finishes first [OK]

Common Mistakes:

• Assuming both succeed creating duplicates
• Thinking server throws syntax error
• Believing client disables form automatically

4. You have this Remix form component:

function MyForm() {
  const transition = useTransition();
  return (
    <form method="post">
      <button disabled={transition.state === 'submitting'}>Send</button>
    </form>
  );
}

Users report the button sometimes stays disabled forever after submission. What is the likely cause?

medium

A. The button should be disabled when transition.state is 'idle', not 'submitting'

B. The server action never returns a response, so transition.state stays 'submitting'

C. The form method should be 'get' instead of 'post'

D. The button needs an explicit onClick handler to re-enable

Solution

1. Step 1: Understand useTransition state

   The transition.state is 'submitting' while waiting for server response, then changes to 'idle' when done.

2. Step 2: Identify cause of stuck state

   If the server action never returns or hangs, transition.state stays 'submitting', keeping the button disabled forever.

3. Final Answer:

   The server action never returns a response, so transition.state stays 'submitting' -> Option B

4. Quick Check:

   Stuck 'submitting' means server response missing [OK]

Hint: Check server response if button stays disabled [OK]

Common Mistakes:

• Disabling button on 'idle' disables it wrongly
• Changing form method unrelated to this issue
• Adding onClick handler won't fix stuck state

5. You want to prevent duplicate form submissions in Remix by combining client-side and server-side checks. Which approach correctly handles this scenario?

hard

A. Only check on server side; client always allows multiple submits

B. Only disable the submit button on client side; server does not need checks

C. Use client-side setTimeout to delay submissions and server accepts all

D. Disable submit button on client during submission and check server if data already exists before saving

Solution

1. Step 1: Combine client and server handling

   Disabling the submit button on the client prevents quick repeated clicks, improving user experience.

2. Step 2: Add server-side validation

   Server-side checks ensure data integrity by rejecting duplicates even if client-side fails or is bypassed.

3. Final Answer:

   Disable submit button on client during submission and check server if data already exists before saving -> Option D

4. Quick Check:

   Client disable + server check = robust duplicate prevention [OK]

Hint: Use both client disable and server validation together [OK]

Common Mistakes:

• Relying only on client disables risks server duplicates
• Relying only on server allows bad UX with multiple clicks
• Using setTimeout delays but does not prevent duplicates