By platform

Jotform this form is currently unavailable

Visitors reach your form and read that it is unavailable, with no way to send anything. Mimiq sends simulated visitors to the form and records the page they see and where they came from.

5 visitors try to .
First test free with an accountRun it from your coding agent

Why does my Jotform say this form is currently unavailable?

Jotform shows that message when the form's own settings say it cannot take entries right now. The usual triggers are a form turned off by hand, a schedule that is not open at the moment the visitor arrives, or a response limit that has been reached. Check those settings in your Jotform account first, then open the form the way a visitor does. A simulated visitor shows whether the message appears on the page the visitor was sent to.

What this looks like in a report

Who
Marisol, booking a Saturday haircut for her nephew's birthday
How they arrived
Opened a booking link from an email reminder on her phone
Where they stopped
Booking page, right after opening the form

“The page says this form is unavailable, with no reason. Maybe the salon is closed this week, or the booking closed early. I need an appointment this Saturday, so I will call instead.”

The fix. Check the form's status, its schedule and its response limit in your Jotform dashboard, and change the one that applies. Then open the link and the embed in a private window to confirm the form loads.

An illustration. Run a test to see your own.See a real sample report

The form is closed in its settings, and the visitor sees only the message

The address your visitor opens, or the embed on your site, pulls the live form from Jotform's servers each time it loads. The form's settings decide whether entries are accepted. A form closed by hand stays shut whatever the time. A schedule opens and closes it at set times, so a visitor who arrives outside the window sees the message even though the form works at other hours. A response limit closes the form once it has collected the number of entries you set. The visitor gets no reason on the page, so the message alone does not tell you which setting closed it.

  • In the Jotform dashboard, read the form's status first and check whether it is set to closed.
  • Look for a schedule on the form and compare its open and close times with the hour the visitor arrived.
  • Check for a response limit, and compare it with the number of entries the form already holds.
  • Open the link and the embed on your site in a private window to see which one shows the message.
  • Confirm the embed points at the form you are editing, not at an older copy of it.

The message appears in two places, and each one needs a different check

Your visitor sees the message either on the Jotform address itself or inside an embed on your own page. On the Jotform address, the whole page is the form, so the message replaces everything, and the address bar shows the Jotform domain. In an embed, the message sits in a box with your headings and buttons around it, so the visitor may think your site is broken. Open both versions in a private window. If only the embed shows the message, the problem may be an old form address in your page, not the form itself.

Closed, scheduled and at its limit: three settings that look the same

The visitor gets no reason on the page, so the three look the same from outside. A scheduled form opens and closes at the times you set, and it can be shut at the hour a visitor finally has time. A limited form stays closed once it has taken the number of entries you set, so the count already in the form is the first thing to check.

A schedule is easy to misread at the hour it matters. A window that looks open when you check it in the afternoon can be closed when a visitor arrives in the evening. Write the open and close times down as your dashboard shows them, then compare them with the hour the visitor actually arrived, not with the hour you last tested. Check that against each visitor you run.

A stale embed keeps pointing at an old form after you duplicate one

An embed on your site carries the identifier of one specific form. If you duplicated the form to make a new version, or rebuilt it, the page may still point at the old one, which is now closed or at its limit. The message is accurate for that old form, which makes the mistake hard to spot. Check the identifier in the embed against the form you are editing, and check whether a second copy of the form is open in your dashboard. Replace the embed with the current one, then test it in a private window.

What the simulated visit records when the form refuses entries

A simulated visitor opens the link or the page with your embed, reads the page, and tries to fill in the form for the task. The run records a screenshot of what the visitor sees, the address it was on when the message appeared, and any script error or failed request on that step. If the message appears, the screenshot shows whether it sits on the Jotform page or inside your own page.

The run cannot read your Jotform settings, so it cannot tell you which trigger is on. Use the screenshot to decide where the message appears, then check the setting in your dashboard. Send the same visitor again after each change, on a phone as well as a laptop, and confirm the form takes an entry before you count the fix as done.

Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

A new schedule or response limit can close the form again

A form closes again each time its schedule ends, its response limit is reached, or someone duplicates it for a new term. Run the same visitor after each of those changes, from the page where visitors arrive. A form that opened on Monday can show the message on Friday evening, so check it at the hour your visitors usually come.

Starter

Try it on one launch

$9 once
120 credits, never expire

About 4 tests of 5 visitors

  • Visitors on your landing page, signup and checkout
  • Where they left and why, with a fix to copy for each problem
  • Run it in the app or on every pull request
  • Ask any visitor a question, included
  • Test accounts and protected previews
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Will reloading the page fix the message?

Not when the cause is a setting. A closed, scheduled or limited form gives the same message on every load until the setting changes. Reloading helps only when a cached copy of your page shows an old message, so try the page in a private window before you change anything else.

Does the message mean Jotform is down?

Rarely. A working service shows that message whenever the form's own settings close it, so the form can be fine on the service and closed on purpose. If the form is open there and the message still appears, check the embed and the page it sits on before you contact support.

Can I tell visitors when the form will reopen?

Yes, on your own page. Put your opening hours and a way to reach you in the text next to the embed. That text belongs to your site, so it stays visible while the form is closed, and visitors know what to do next.

Can the simulated visitor tell me which setting closed the form?

No. The run shows the message, a screenshot of the page with it, the address it appeared on, and any error recorded on that step. It cannot open your Jotform settings, so it cannot read the schedule or the limit. It also does not tell you how many visitors would have sent an entry if the form had stayed open.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.

5 visitors try to .