ImmiAccount error messages, system outages, and what they actually mean

Migratio Editorial · Last updated 24 July 2026

TL;DR: ImmiAccount displays a range of error messages from session timeouts to payment failures, and most have straightforward fixes. This guide lists exact error strings, explains what triggers each one, and covers how to tell whether the system is down or the problem is on your end.

Few things are more stressful than hitting an error screen in the middle of a visa application. ImmiAccount displays a variety of error messages — some caused by system maintenance, some by browser configuration, and some by payment processing failures. The trouble is that the messages themselves are often vague, leaving users unsure whether to wait, retry, or start over. This guide catalogues the most common error strings users encounter, explains what each one actually means, and walks through the steps to resolve them. If you are new to the system, the ImmiAccount setup guide covers account creation, login, and multi-factor authentication. Come back here when something goes wrong.

"System is currently unavailable"

This is the most frequently reported ImmiAccount error. The full message typically reads: *"The system is currently unavailable. Please try again later."* It appears when the Department's servers are down for scheduled maintenance or experiencing unplanned outages. There is no action you can take to bypass it — the system is genuinely offline.

Scheduled maintenance usually occurs on weekends, most often Saturday evenings through to early Sunday morning (AEST/AEDT). The Department sometimes posts advance notice on its systems status page, but not always. If you see this message during a weekday business-hours session, it is more likely an unplanned outage. Wait 15 to 30 minutes and try again. If the outage persists beyond an hour during business hours, check the Department's official systems status page for updates.

"Session has timed out"

The full message is typically: *"Your session has timed out. Please log in again."* ImmiAccount sessions expire after a period of inactivity — generally around 30 minutes, though the exact threshold is not published. If you step away from your computer or spend a long time gathering documents before clicking the next button, you may return to find this error.

Any unsaved data in the current page will be lost. However, data saved on previous pages using the "Save" or "Next" button is retained. To reduce the risk, click "Save" frequently as you work through each page of an application. After a timeout, log back in through the ImmiAccount login page and navigate back to your application.

"An error has occurred"

This generic message — *"An error has occurred. Please try again later."* — is the system's catch-all. It can appear during form submission, document upload, or payment. Because it is non-specific, troubleshooting requires a process of elimination:

1. Clear your browser cache and cookies, then try again.
2. Switch browsers. ImmiAccount officially supports recent versions of Google Chrome, Microsoft Edge, Mozilla Firefox, and Safari. If you are using an older or unsupported browser, this error may appear during form rendering.
3. Disable browser extensions. Ad blockers, privacy extensions, and translation plugins can interfere with ImmiAccount's scripts.
4. Check your file. If the error appeared during a document upload, confirm the file is under 5 MB, the filename contains only letters, numbers, dashes, and underscores, and the file is not an encrypted or form-fillable PDF. See the upload rules in the ImmiAccount guide for full details.
5. Try again later. If none of the above resolves the issue, the error may be server-side. Wait 30 minutes and retry.

After multiple failed login attempts, ImmiAccount locks the account for 4 hours. The message reads something like: *"You have exceeded the maximum number of login attempts. Your account has been locked."* You cannot reset the lockout timer — you must wait the full 4 hours before trying again.

Before your next attempt, verify your username (it is the email address you registered with) and reset your password through the "Forgot password" link if needed. Since 18 June 2025, multi-factor authentication (MFA) is mandatory, so ensure your MFA device is accessible. If you are consistently locked out, confirm that no one else is attempting to log in with your credentials — shared email accounts are prohibited under the Terms of Use (sections 5.1 and 5.6).

Payment processing errors

Payment errors are among the most anxiety-inducing because applicants worry about being charged without the application being submitted, or about the application being rejected due to non-payment. Common payment-related messages include:

- *"Payment could not be processed. Please try again."* — This typically means the card issuer declined the transaction. Check that your card has sufficient funds, that international transactions are enabled, and that the card has not expired. ImmiAccount accepts Visa, Mastercard, and some other payment methods.
- *"Transaction declined"* — Contact your bank or card issuer. Australian visa application charges are processed as international government transactions, and some banks flag these as suspicious by default.
- *"Payment has been received but the application was not submitted"* — This rare but serious situation means the payment was debited but the application status did not update. Do not pay again. Contact the Department through ImmiAccount's messaging function or by phone. Case law — including the Cabrera and Kaur decisions — has examined circumstances where payment failures or processing errors affected application validity, which underscores the importance of keeping payment receipts and screenshots.

After any payment error, check your bank statement before retrying. If the charge appears, do not attempt a second payment without first confirming with the Department whether the original transaction was received.

ImmiAccount relies on JavaScript and cookies. If either is disabled, the system may not load correctly or may display blank pages with no error message at all. Common browser issues include:

- Blank white page after login. Usually caused by disabled JavaScript or a strict cookie policy. Enable both, then reload.
- Buttons not responding. Often caused by browser extensions. Try an incognito or private browsing window with extensions disabled.
- "This page can't be displayed" or SSL/TLS errors. These indicate a connection problem. Check your internet connection, try a different network, or confirm that your browser's security settings have not been manually restricted.
- PDF viewer errors. When trying to view or download a grant letter or correspondence, some browsers' built-in PDF viewers fail. Download the file directly instead of opening it inline.

For the most reliable experience, use the latest version of Google Chrome or Microsoft Edge with JavaScript enabled, cookies allowed for `online.immi.gov.au` and `immi.homeaffairs.gov.au`, and all browser extensions temporarily disabled.

How to check if ImmiAccount is down

When you encounter errors, the first question is whether the problem is system-wide or local to your setup. Steps to determine this:

1. Check the Department's systems status page. Visit the Departmental systems page for any posted outage notices.
2. Try a different browser or device. If the system loads on another browser, the problem is your browser configuration.
3. Check third-party status monitors. Sites like Downdetector aggregate user reports and can indicate whether other users are experiencing the same issue in real time.
4. Note the time. If it is a Saturday evening or early Sunday morning (AEST), scheduled maintenance is the most likely cause.

If the system is confirmed down, there is nothing to do but wait. Do not repeatedly attempt to submit an application during an outage — this will not queue your submission and may cause duplicate payment attempts.

Maintenance windows and planned downtime

The Department does not publish a fixed maintenance schedule, but based on historical patterns, planned outages most commonly fall on:

- Saturday evenings from approximately 8:00 PM to Sunday early morning (AEST/AEDT)
- Public holiday weekends, particularly around end-of-financial-year (late June) and Christmas/New Year periods
- Mid-week windows for urgent patches, usually brief (under an hour) and sometimes unannounced

If you are working on a deadline — such as responding to a request for information or completing a time-limited invitation — avoid leaving submission to the last hour. System outages during deadline periods do not automatically extend your deadline, though you may be able to explain the delay if you can provide evidence that the system was unavailable.

Compare MARA-registered migration agents — free