CBSA published TCC26-0125 last week: the eManifest Portal will force re-authentication every hour on Saturday August 8 and Sunday August 9, 2026, from 06:00 to 07:00 ET each day. The portal itself stays online. You can still create and submit all ACI trade documents (M3, X30, A8A/A8B), update user access, query cargo control numbers. You just get booted to the login screen mid-session.
This is not a blackout. It's not an outage. It's a rolling authentication reset during a low-volume weekend while CBSA patches something backend. Most brokers won't even notice unless they're filing Sunday morning highway manifests or cleaning up Friday night's rejected X30s.
But the notice says "follow your System Outage Contingency Plan," which makes it sound worse than it is. Let's walk through what that actually means and what you should prep.
What the SOCP Is (and When You Actually Use It)
Your System Outage Contingency Plan is the paper fallback you file with CBSA when the eManifest portal, EDI gateway, or your own software dies hard enough that you can't transmit ACI within the regulatory window. The SOCP covers how you'll notify CBSA, how you'll track cargo control manually, and how you'll backfill the electronic submission once the system comes back.
You invoke it when the portal is down, not when you have to log in twice. CBSA's notice is boilerplate CYA language. If the portal were actually unavailable for the full 24-hour window, yes, you'd notify your local CBSA office and fall back to paper manifests under D3-1-1. But forced re-logon with full document submission capability does not meet that threshold.
The real SOCP trigger is: can you file an M3 for a truck crossing the border in 90 minutes? If yes, you're fine. If the login screen won't let you through after three tries and your highway carrier is 40 minutes from the booth, then you call CBSA and invoke contingency. A one-hour maintenance window on a Sunday morning is not that scenario.
What You Should Actually Prep
Batch your weekend filings before 06:00 Saturday if you can. If you have X30s or A8As to clean up from Friday's rail movements, file them Friday night. If you have advance M3s for Sunday afternoon highway freight, queue them Saturday evening after the first maintenance window closes at 07:00 ET.
Expect login friction, not submission failure. The notice says "forced re-logon" — that means session timeout, not credential rejection. You log back in with the same username and delegated client access. Your half-finished M3 draft might be gone if you didn't save it, but the system will accept new submissions the moment you're back in. Keep your credentials and 2FA device handy.
If you're running a Sunday morning highway operation, warn your dispatch team. A truck arriving at Lacolle or Peace Bridge at 08:00 Sunday needs the M3 filed by 06:00 (one hour pre-arrival minimum under ACI requirements). If the portal boots you at 06:45 and you have to log back in, you've still got 15 minutes of buffer. Tight, but not impossible. The real risk is if your broker doesn't check their session until 07:50 and the M3 is still sitting in draft.
Have paper copies of your cargo control log. This is baseline SOCP hygiene, not specific to this maintenance window. If the portal goes dark for real — not a forced re-logon, but an actual 503 error that won't resolve — you need a way to assign and track CCNs manually so you can backfill the ACI records once the system is live again. Most brokers keep a spreadsheet or a paper ledger. If you don't, this is a reminder to build one.
Warehouse Coordination (If You're Clearing to a Bonded or Sufferance Facility)
If your consignee is a Montreal sufferance warehouse or another bonded site, the eManifest filing is the first domino. Miss the ACI window and the truck shows up without a valid cargo control number. CBSA won't release it. The container sits on the chassis. Drayage detention starts accruing. The warehouse can't accept it into their systems because there's no PARS or RMD to key against.
A one-hour login interruption on a Sunday won't cause that cascade if you filed the M3 Saturday night. But if you're a high-volume importer running cross-border freight seven days a week, make sure your 3PL or internal logistics team knows the portal might hiccup. The drayage dispatcher should confirm with the broker that the ACI is live before dispatching the truck to the border. That's a good practice anyway; the maintenance window just makes it non-negotiable.
What Happens If You Miss the Window Anyway
Let's say the portal boots you at 06:50, you can't get back in until 07:05, and your truck is at the booth at 07:30 with no M3 on file. CBSA will likely hold the truck for manual processing. The driver presents paper docs. The officer keys the entry manually or calls your office. You file the M3 retroactively once you're back in the portal. CBSA may flag it for audit, but as long as you can show the portal was under maintenance and you attempted to file within the regulatory window, you're not looking at an AMPS penalty under A11 of the Customs Act.
That said, "the portal was down" is a better defence than "I forgot to check my session." If you're filing Sunday morning highway freight during a known maintenance window, log in early, file early, and don't assume your session will hold for an hour.
Rolling Maintenance Is the New Normal
CBSA has been doing more of these short rolling maintenance windows since CARM went live. The old B3 world had longer blackout windows, usually overnight or early Sunday morning, and brokers just worked around them. The CARM-era CAD filing system runs on a different stack, and CBSA is patching it more frequently with shorter, more surgical downtimes.
From an operational perspective, that's better. A forced re-logon every hour for two one-hour windows is easier to plan around than a six-hour hard blackout. But it does require you to stay alert. If you're used to the old rhythm where "Sunday morning = no filings," that assumption doesn't hold anymore. CARM runs 24/7, and so does the expectation that your ACI is filed on time.
Most of the time, these maintenance windows are non-events. The portal stays up, you get logged out once or twice, you log back in, you keep working. The only time it becomes a real problem is if you're cutting your ACI filing close to the arrival window and the forced logon happens at exactly the wrong minute.
Don't let the "follow your SOCP" language spook you. CBSA legal has to say that. In practice, if the portal is accepting submissions, you're not invoking paper contingency. You're just refreshing your login and getting on with it.
If you want a second set of eyes on your ACI workflow before the next maintenance window, or you're still filing PARS manually and want to move to automated eManifest submission, that's a workflow audit we run every week. Get in touch.
Originally published at https://www.canflow-global.com/en/insights/emanifest-portal-maintenance-aug-8-9-forced-re-logon-not-a-blackout/.
Top comments (0)