One more screen described a symbol ratio the wrong way — the repeater detail page, which the previous correction missed.
- —The repeater detail page still said a custom symbol ratio "overrides" your multiplier. It is the same correction as v1.6.1, applied to the one screen that pass missed: the ratio multiplies with your sizing, so a 2× multiplier and a 0.5 ratio size that symbol at 1×. Nothing about how trades are sized has changed — only the description.
Two of the sizing descriptions in the app were wrong about what your settings do. The engine never behaved the way they described — but the wording may have led you to size a symbol differently than you meant.
- —Corrected what the app says a symbol mapping's ratio does. It said a custom ratio overrode the multiplier for that symbol. It has always multiplied with it: a 2× multiplier and a 0.5 ratio size that symbol at 1×, not 0.5×. If you set a ratio expecting it to replace your multiplier, copies on that symbol have been larger than you intended — worth re-checking any mapping where you changed the ratio. Nothing about how trades are sized has changed; only the description was wrong. The warning shown next to the multiplier now says so, and appears in equity-ratio mode too, where a ratio applies just the same.
- —Corrected the Max Volume description. It said it capped the volume a follower could hold on a symbol at once, which reads as a limit on your total position. It caps each individual copy, so several copies on the same symbol can still add up past it.
An honest comparison with TradersConnect, and repeater changes now pass the same checks whichever route they arrive by.
- —A comparison guide for TradersConnect, written the same way as the others: it says plainly that TradersConnect is cheaper for copying alone and covers ten platforms to Trepeat's two, then shows what the totals look like once you count the trade analytics it charges separately and Trepeat includes — Trepeat is cheaper at two accounts, level at around five, and dearer at ten. It also states up front that Trepeat connects demo-server accounts only, so nobody wastes time comparing the rest if they need a live account.
- —Every change to a repeater now passes the same server-side checks whichever route it arrives by, so the rules you see in the app are the rules that actually apply. Nothing changes in how you use Trepeat.
Each repeater sets how long a follower's broker has to confirm a copy, copies wait for a follower that is still connecting, and a shorter free trial.
- —Order confirmation limit: each repeater now sets how long a follower's broker has to confirm a copied order, from 1 to 30 seconds (5 by default). A confirmation later than this still counts as a failed copy, and a position the broker opens late is closed, because its price may be far from the source's. Find it with the other sizing settings.
- —The free trial is now 7 days for new subscriptions. If you are already on a trial, it keeps its original length.
- —During a free trial you can make up to 3 new broker-account connections, on every plan. Accounts you remove still count, and your plan's full allowance applies once the trial ends. The limit is shown on the plans, at checkout and when you add an account.
- —While a repeater is starting, it now says a first connection can take a minute or two, and that trades placed before it shows Running may not be copied.
- —A symbol mapping that would change nothing (the same symbol at 1×) can no longer be saved, so a repeater never looks configured when it is not. A mapping that keeps a symbol's name for one follower, or changes only its ratio, still saves.
- —Deleting your account now behaves the same from Settings and from the subscribe page. If your account was already deleted, you are signed out cleanly instead of being asked to try again, and an expired session asks you to sign in again.
- —Red buttons and error text are easier to read.
- —A trade that arrives while a follower account is still connecting now waits for it, up to the repeater's order confirmation limit, instead of being missed straight away.
- —One notification per missed copy: a follower that wasn't ready no longer raises a second alert, and when a slow order is filled late and closed, that alert replaces the earlier "order failed" one instead of adding to it.
- —A copy missed because a follower account wasn't connected now says so in plain words, and says whether it was still connecting.
- —On Trades, a trade copied to several followers where only some copies failed now says how many, for example "1 of 2 copies" under Failed, instead of reading as if every copy failed.
- —If Trepeat couldn't connect an account and it ended up stopped rather than in error, the account now shows when the last attempt failed and why, instead of just "Standby".
- —A "couldn't close a copied position" alert now clears itself once the account reconnects and the position is confirmed closed at your broker, instead of staying in your notifications after you have dealt with it.
- —Symbol mapping suggestions now use each broker's own description of its symbols, so Trepeat can offer the right name — and stops warning that a correct mapping looks wrong — even when a broker names or decorates an instrument in a way no list anticipated.
- —Some errors could show technical text, such as part of a server error page, instead of a plain message. They now show a clear message.
- —Tightened a server-side check so your plan usage details (plan, account count and extra slots) can only ever be read by your own account.
The repeater page now shows everything its settings control, and a few messages stop giving advice that did not fit.
- —A repeater's page now shows its full setup: which follower each symbol mapping applies to, whether it sizes by multiplier or by equity ratio, and the rounding rule in words. It also warns when a mapping can never run because its symbol is not in your Symbol Allowlist. Previously a repeater using equity ratio showed only a multiplier, and two mappings for the same symbol on different brokers looked like a contradiction.
- —Your repeater history and the Repeaters export now say which follower a symbol mapping applies to, and the export includes the sizing mode.
- —While Trepeat is automatically reconnecting an account, its "disconnected" notification no longer tells you to reconnect it yourself — it says a retry is under way, matching the repeater's own alert.
- —When a copy fails because your own symbol mapping sends a follower the wrong name, and that follower already trades the original, the alert now tells you how to fix that mapping — remove it, or keep the original name for that account so your other followers are unaffected — instead of suggesting you map a symbol to itself.
- —A mapping that keeps a symbol's name for one follower, while your other followers use a different name, is no longer flagged as "doing nothing" — it is exactly how that follower keeps its own name.
- —The recent security activity list in Settings could skip a block of events if it refreshed while you were scrolling to load older ones.
- —The "Account disconnected" email setting now mentions that it also covers the email sent when automatic reconnects run out.
An account that loses its broker connection is now retried on its own, and reconnecting it no longer asks for a password it never needed.
- —When an account can't reach its broker, Trepeat now retries the connection on its own — up to three times over about an hour — and the account row shows when the next try is. Previously nothing retried: a short broker outage left the account in an error state until you noticed. If a retry works, you get a notification naming the repeater to run again; if all three fail, you get an alert and an email saying so, with what to do next. Repeaters are not restarted automatically, because prices may have moved while the account was offline — that stays your decision.
- —Reconnecting an account that couldn't reach its broker no longer asks for your password. Your saved login was never the problem, so the dialog now offers to reconnect with it. You can still enter a different password if you want to.
- —When a repeater stops because one of its accounts can't reach the broker, the alert now tells you Trepeat is retrying and what to do once it's back, instead of saying the alert would clear once the account was healthy — which nothing made happen.
- —The alert for a stopped repeater named something like "Repeater A" read "Repeater Repeater A stopped". It now uses the name exactly as you wrote it.
Symbol mappings can now target a single follower, so repeaters spanning two brokers can be configured correctly.
- —A symbol mapping can now apply to one follower account instead of all of them. If your followers are at different brokers that spell the same instrument differently — XAUUSD on one, GOLD on another — you can now set the right target for each. Previously one mapping had to serve every follower, so a repeater spanning two brokers had no correct setting at all. Mappings you already have keep applying to every follower, exactly as before.
- —When a mapping targets one follower, the target list now shows that broker's own symbols. The old list only offered symbols every follower shared, which is exactly where the name you needed was missing.
- —Symbol Mappings has moved out of the collapsed "Advanced" section and now sits directly under Symbol Allowlist. It is what makes copying between two different brokers work, so it should not have been hidden.
- —Searching for a symbol now finds it under the other broker's name. Type XAUUSD and you will see GOLD if that is what your follower's broker calls it — and when Trepeat can tell, it now suggests that name for you while you are setting the mapping up, instead of only after a copy has failed.
- —Adding a symbol to your Symbol Allowlist could silently delete symbol mappings you had already set up. Nothing warned you, and there was no way to get them back. Mappings are now kept: if one refers to a symbol your allowlist blocks, Trepeat says so and offers to add that symbol to the allowlist for you.
- —The Symbol Allowlist only offered symbols that every follower account happened to trade under the same name. That excluded symbols your followers CAN receive through a mapping — so setting an allowlist could quietly stop a repeater copying anything. It now lists your source account's symbols, and tells you if a follower cannot receive one.
- —Creating a repeater through New Repeater did not offer the per-follower symbol options that the settings panel does, so a repeater spanning two brokers could not be set up correctly until you opened its settings afterwards. The create and settings panels now behave identically.
- —Symbol suggestions could point at the wrong instrument — offering gold priced in euros, or Bitcoin Cash, when you meant gold in dollars or Bitcoin. Trepeat now only treats two names as the same instrument when the difference is a broker's own suffix.
- —Reconnecting an account that had failed asked for your password twice. The first reconnect worked, but the account still showed the old error afterwards — so it looked like nothing had happened, and the message on screen suggested deleting the account and adding it again. One reconnect is now enough, and the error clears when it succeeds.
- —Clicking Reconnect immediately showed "your broker is taking longer than usual to respond", before the broker had been given any time at all. The notice now only appears once the connection really has been running for a couple of minutes.
- —Your broker's symbol list is now loaded when you add the account, instead of only after a repeater had run. Previously you had to start copying — and let copies fail — before you could set up a symbol mapping to prevent those failures.
- —When a copy fails because a follower's broker names a symbol differently, the suggested fix now tells you to add the mapping for that account only. It used to suggest changing the mapping for every follower, which would have broken the followers that were copying correctly.
- —Adding a follower account in a repeater's settings briefly flashed a warning telling you to start the repeater to load its symbols. The warning was wrong — the symbols were simply still loading — and it no longer appears.
- —When a connected account's symbol list could not be loaded, Trepeat told you to start the repeater or reconnect — even though the repeater was already running and the account was already connected. It now says what is actually happening: the symbols could not be fetched from your broker, and we are retrying on our own.
Adding a broker account no longer fails just because your broker is slow to respond.
- —If your broker took more than about four minutes to finish connecting when you added an account, Trepeat gave up and marked it as failed — and then told you to check your server name, even when it was correct. Trepeat now keeps waiting for as long as it can, and only asks you to check your login details when your broker actually refused them.
- —An account that is still connecting after a couple of minutes now tells you it is just taking a while, instead of showing a spinner with no explanation.
Symbol remapping works end to end — the right target is now selectable, and Trepeat names it for you.
- —If your follower broker rejected a copy because it spells an instrument differently — gold as XAUUSDm rather than XAUUSD, say — Trepeat was meant to name the symbol your account does offer so you could add a symbol override. In the most common case it stayed quiet and reported only that the symbol was unavailable. It now names the symbol whenever your follower account carries the instrument under another name.
- —The Target list when mapping a symbol only offered instruments your SOURCE account carries, so if your two brokers spelled an instrument differently the name you actually needed was never in the list. It now lists what your follower account offers, which is what a mapping is for.
- —A mapping whose source and target are the same symbol does nothing at all, and nothing said so. It is now flagged as you build it.
- —When your broker confirmed an order too late for Trepeat to use, Trepeat closes that late fill so you are not left in a position the source never intended. If that close attempt itself timed out, it gave up on the first try and the position stayed open. It now retries before asking you to close it by hand.
- —A follower account whose connection failed part-way could leave a dead connection behind, which in turn could slow or stall later reconnection attempts for that account. Failed connections are now cleaned up straight away.
Clearer sign-in wording, and deleting your account now shows you it is happening.
- —The sign-in page said that entering an email address there would create an account if you didn’t have one. It doesn’t — signing in and signing up are separate, and an unrecognised address is sent to the sign-up page instead. The wording now says that.
- —Deleting your account looked like nothing had happened. The confirmation box closed immediately and left you on the page you were already on, with your account menu still showing, until the deletion finished. It now shows a clear in-progress screen and takes you out of the app when it completes.
- —If deleting your account failed, you were shown no error at all — the message was attached to the box that had already closed. Failures are now visible, and the technical detail that was occasionally shown in its place is not.
- —A few error messages came straight from the database rather than from us, so instead of an explanation you could be shown internal technical detail. Saving your recovery codes was the clearest example. Those now say what went wrong in plain terms, while the messages we write for you — the ones that tell you a code is invalid, or that you need to sign in again — are unchanged.
- —After deleting your account you were returned to the sign-in screen with no confirmation that anything had happened. The confirmation was being written and then discarded before the screen finished loading. It now appears.
- —Reported by Ganesh RK, who also prompted a review of how our error messages are shown. Thank you.
Four things Trepeat told you wrongly when a copy didn’t close — including an outcome it invented.
- —The dashboard reported a break-even on trades whose result Trepeat could not actually determine. When a position closes without Trepeat seeing it, the profit or loss genuinely cannot be recovered from the broker, and Trepeat deliberately records nothing rather than guess — but the dashboard was reading that missing value as zero and showing a confident “BE”. It now shows “Unknown”, which is what the Trades page already showed for the same trade. If you saw a break-even you could not explain, this was why.
- —When a copied position couldn’t be closed automatically, the alert said Trepeat had been briefly offline. That was wrong. In the case that prompted this, Trepeat had been running for three days without interruption and was retrying throughout — it was the connection to the broker that dropped. The message now says what actually happened: the close wasn’t seen live, usually because the broker connection dropped for a moment. What to do about it is unchanged — close the position on your broker, because Trepeat deliberately never closes it later at a price that has moved on.
- —The same wrong explanation appeared on the Trades page. A trade whose outcome couldn’t be recovered showed a tooltip blaming a Trepeat outage; it now says the close wasn’t seen live, for the same reason.
- —Stopping a repeater said open trades “stay tracked”, which read as reassurance. Stopping a repeater disconnects its accounts, and Trepeat can’t close a position while the account is disconnected — so anything open at that moment stays open at your broker. The message now says that plainly, and gives you both ways out: close it at your broker, or run a repeater again to reconnect and use Flatten.
An account that stops connecting can be fixed again without deleting it.
- —When an account stopped connecting to your broker and was then set aside, the message explaining what went wrong stayed on screen but the way to fix it disappeared — you could re-enter your password while the account showed an error, and no longer could once it went to standby. The password field is back, so you can fix the login in place instead of deleting the account and adding it again.
- —A connecting account showed a grey dot beside its amber “Connecting” label, which read as inactive rather than in progress. It now pulses amber like every other in-progress state.
Connection problems tell the truth, and every one of them now has a way out.
- —When reconnecting a broker account timed out, the message said we couldn’t reach our own connection service — which sent people off to check whether Trepeat was down. In practice the request reaches us fine and it is the broker platform that does not answer in time, usually because the login itself is no longer valid. It now says that. The two things that matter are unchanged and still true: your account is left exactly as it was, and trying again is the right next step.
- —Reconnecting an account that had been put back into standby while you were away no longer asks for a broker password it gives you nowhere to type. It reconnects from the credentials already saved against the account.
- —An account could be wrongly reported as deleted at your broker. A single momentary failure to reach the broker platform was enough to mark the account gone, and the message never went away on its own — even though the account was fine the whole time. We now confirm against a second source before saying an account is gone, and any account wrongly marked this way is put right automatically.
- —An account sitting on Standby because something was genuinely wrong showed the reason but no button to act on it — the only way forward was to start a repeater and let it fail. It now offers Reconnect directly.
Connection badges now say which stage a broker link is actually at.
- —An account whose broker link drops used to show “Reconnecting” for the entire time it was down — whether that was thirty seconds or three days. It now says what stage it is actually at. For the first five minutes it reads “Connecting”, because that is what is happening: a broker handshake takes three to five minutes, and an account that has just started up is not broken. After that it reads “Unstable”, alongside the “Re-enter login” button, because by then something is wrong and waiting may not fix it. Past two hours it still reads “Can’t reach”. The old wording was also one letter away from “Connecting” while meaning the opposite, so two accounts starting up together showed two different words for the same thing.
A dead broker connection now keeps telling you it is dead.
- —When a repeater stopped itself because a broker account was unreachable, the account row went quiet: the “Can't reach” state and the “Re-enter login” button both disappeared, leaving a plain “Standby” badge and no way to tell that the login was the problem. Stopping a repeater disconnects its accounts, and the app was reading that disconnection as the account having recovered. It now keeps showing how long the connection has been down, and the button to re-enter your login, until the account genuinely reconnects.
- —The same went for accounts that failed for other reasons — an expired demo, a login the broker no longer recognises. The explanation was attached to the account only while it sat in an error state, so the moment a repeater stopped and disconnected it, the text was thrown away. Whatever we know about why an account is unreachable now stays with it until it genuinely reconnects.
- —The matching alert had the same flaw and was worse: “Repeater auto-stopped because an account is unavailable” resolved itself a couple of seconds after appearing, because stopping the repeater looked like the account getting better. In practice you would never see it. It now stays on the alerts page until the account is actually reachable again.
A limit on how many new broker accounts can be connected in a 30-day period.
- —There is now a limit on how many NEW broker accounts you can connect in any 30-day period — 6 on Starter, 12 on Growth, 24 on Scale. Connecting an account costs us a one-off setup fee that is not refunded if the account is later removed, so accounts you have since removed still count toward the limit. That is the part worth knowing, because it is the only way the limit can surprise you. The Add Account dialog shows how many connections you have left once you are near it, and refuses clearly rather than failing halfway. The limits sit well above normal use — they exist to bound repeated connect-and-remove cycles, not to get in the way of setting up your accounts. If you need more, email support@trepeat.com.
The symbol-mapping warning stops going quiet on pairs it should flag.
- —When you map one symbol to another, we warn you if the two look unrelated — mapping gold to a currency pair is almost always a mistake, and a wrong mapping means copies fail. That warning was silently skipping itself whenever a symbol happened to contain the letters of a short instrument code, so pairs like XAGCAD → GOLD were waved through as related. It now matches whole names and broker suffixes rather than any letters it finds in the middle, so the warning appears when it should.
- —If you accept analytics cookies, we now record how you first found us — the campaign tags on the link you clicked, the site that linked to us, and the page you landed on — once, against your account. It is never updated afterwards, we store the referring domain only and never the full address, and declining changes nothing about how the app works. The privacy and cookies policies describe exactly what is kept.
Getting started no longer dead-ends when you've connected one account.
- —A repeater copies trades between two of your accounts — the one you trade on and the one that mirrors it — so it needs both connected before anything can happen. With only one, the app never said so. The Repeaters page offered to create a repeater, and the second step of that form showed an empty list of follower accounts next to a greyed-out button, with no explanation. Both places now tell you a second account is needed and take you straight to the page to add one.
- —The welcome checklist said "Connect your first account", which was the only hint that a second one was coming, and it ticked itself off as soon as you had one — telling you that you'd finished the very step that was blocking you. It now reads "Connect two accounts", explains what each is for, and stays unticked until both are connected. It also no longer counts accounts or repeaters you've archived.
When a copy fails, it now tells you how to fix it — and tells you at all.
- —If your follower broker doesn't offer a symbol under the name your source broker uses, the copy fails with "Unknown symbol" — true, and no help at all unless you already knew Trepeat has symbol overrides. Brokers genuinely disagree here: the same gold can be XAUUSDm on one and GOLD on another. The alert now checks what your follower account actually offers and names the mapping to add, for example "This account does offer XAUUSD — add a symbol override mapping XAUUSDm to XAUUSD". It only ever suggests a symbol your follower really has, and never changes an order itself: which instrument you trade stays your decision
- —A symbol that keeps failing used to raise a separate alert every single time, so one misconfigured symbol could bury everything else in your bell. You now get one alert per account and symbol, which stays until you deal with it and comes back if it happens again after you dismiss it. Every failed copy is still recorded on your Trades page — only the repeated alert is collapsed, never the record
- —Copies failing repeatedly now send you an email. Previously they never could, so it was possible for a session to fail from start to finish while your inbox stayed silent and the only mail you got was about the repeater stopping afterwards — the consequence, not the cause. It sends once the same symbol has failed several times in an hour, so a one-off broker hiccup won't mail you, and you can turn it off under Settings → Email
- —When we can't confirm a broker account is a demo account, the message said only "please try reconnecting" — which cannot work if the reason is the server name. It now asks you to check the server name matches your MT4/MT5 terminal exactly, and points out that a web address isn't the same thing as a server name
- —Product update emails are now off unless you turn them on. The setting existed and was switched on by default, though nothing had ever been sent through it. Before we start sending release notes, an on-by-default switch isn't a choice you made — so it's off for everyone, and it's yours to turn on under Settings → Email if you want to hear when we ship something
A broker account we can't connect to now tells you what to actually do about it.
- —When we couldn't connect to a broker account, the error read "Restart the repeater to retry" — advice that cannot work if the account itself has gone. Demo accounts expire, and restarting simply failed again and showed the same message, so it was possible to loop for days without learning anything. It now says we couldn't connect, and names the two real causes: a demo account that has expired and needs replacing, or a broker that is temporarily unreachable. We don't claim to know which — your broker reports both the same way — so it gives you the likely one first rather than guessing
- —When a repeater stopped itself because one of its accounts went unhealthy, the email always said the SOURCE account was the problem. It fires for a follower just as often, so anyone whose follower failed was sent to check the one account that was working fine. It now names neither role, and the details below it identify the actual account
- —An account whose broker connection stays down for more than two hours now reads "Can't reach" with how long it has been out, instead of an amber "Reconnecting" badge that never changed. Reconnection attempts continue in the background either way, so an account that comes back still recovers on its own with nothing for you to do
The sign-up form now catches email typos before they cost you the link.
- —Mistype your email domain when signing up — gmail.con instead of gmail.com, say — and the form now offers the correction for you to click. Before this, nothing flagged it: the sign-up link went to an address that does not exist, no error appeared on screen, and the only clue was an email that never arrived. It is a suggestion and never a block, so an unusual but genuine address still goes straight through. This already worked on our waitlist form and simply had never been connected to the sign-up form
A correction to what our Privacy Policy says about how long we keep server logs.
- —Our Privacy Policy said server logs are kept for 90 days. That was not accurate for every service — depending on what the log is for, we keep them for one, three or six months, and one log had no expiry set at all. The policy now states the real maximum (up to six months) with the reasoning, and the missing expiry has been set to one month. We found this ourselves while checking our published commitments against what our systems actually do
Disconnection alerts stop repeating, and a broken account can't quietly silence another one.
- —If an account stays disconnected, you now get at most three alerts about it rather than one every six hours indefinitely. If it recovers and breaks again, that counts as a new problem and you are told again
- —If two of your accounts share the same name, one of them reconnecting could clear the other's disconnection alert — leaving an account that was still down with nothing showing. Alerts are now tied to the specific account
The disconnection alert no longer fires at someone who has already fixed it.
- —The “account disconnected” email added in 1.4.13 could arrive about a minute AFTER you reconnected an account, telling you it had been down for over half an hour. It now waits until an account has genuinely been connected that long before saying anything, so fixing the problem ends the alerts instead of triggering one
An account that has lost its broker connection now says so, instead of showing a green dot.
- —If an account stays disconnected from your broker for more than half an hour, you now get an alert and an email. Previously that state was silent — an account could sit unable to copy for days with nothing telling you, because the account still looked connected everywhere else. You can turn the email off under Settings → Notifications
- —The notification setting “Source account disconnected” is now “Account disconnected”. It used to cover only accounts driving a repeater; it now covers followers and accounts not in a repeater yet. If you had already switched it off, it stays off — and it now silences those too
- —If your broker login stopped working — revoked, changed, or removed at the broker — the account could keep showing a green “Connected” dot while nothing was actually copying. It now shows “Reconnecting”, which is the honest state
- —When an account connected but its symbol list failed to load, that list stayed empty for good, and the Symbol Allowlist told you to start the repeater or reconnect the account — neither of which could actually reload it. The list is now retried automatically until it loads
- —Changes to a repeater — sizing, symbol rules, adding a follower — apply instantly again. They had been taking up to 30 seconds to reach the copy engine
- —If your broker rejects a connection attempt, we pause retries on those exact details so a failing connection is not tried over and over. You can now retry the same details after about an hour, which matters when the rejection was your broker being briefly unreachable rather than anything wrong with your login. Changing any detail clears the pause immediately
Withdrawing cookie consent now sticks — across open tabs, and for good.
- —If you withdrew cookie consent on our main site while the app was open in another tab, that tab carried on as before until you navigated somewhere. Consent now applies across every open tab the moment you return to one
- —A withdrawal could undo itself. We record your choice in two places, and only one of them was being updated — so once the shared record expired, the older copy could take over and switch analytics back on. Both are now kept in step, and a withdrawal stays withdrawn
If a payment fails, copying stops and you are told why.
- —When a payment failed, your repeaters kept copying while you were locked out of the app — unable to stop one or check your fills. Copying now stops when the payment does, and the page explains what happened. Positions already open stay at your broker, where you can manage them as usual
- —A failed payment now sends its own email saying what stopped and how to restart it, instead of one that read as though the subscription had been cancelled
- —Trades left open when a connection closes are now marked closed with no result, rather than sitting in your history as permanently open
If checkout fails to load, it now says so and offers a retry.
- —When the checkout page failed to load, it showed an empty space — no error, no explanation, and no way to try again short of navigating back and starting over. It now tells you what happened, confirms your card has not been charged, and gives you a Try again button
- —If an ad blocker, privacy extension or company network blocked our payment provider from loading, checkout was blank with no clue why. It now names the cause and tells you what to allow
Adding an account on your phone works again, and pages stop pretending to load forever.
- —On a phone, the Add Account form could be taller than the screen with no way to scroll — so the button that submits it was out of reach and you simply could not connect an account. Every dialog in the app now scrolls when it needs to
- —Opening a page from the sidebar kept the scroll position of the page you left, so you could land halfway down instead of at the top
- —When data was slow to arrive, pages showed loading placeholders indefinitely with no explanation. They now tell you it is taking longer than usual, and keep waiting rather than giving up on data that is still on its way
- —If the connection dropped while the payment page was loading — easy on a phone — it failed outright with no way forward except starting again. It now waits, and retries once before giving up
- —Buying or removing an extra account slot could keep waiting indefinitely if your connection dropped, leaving you watching a spinner with no idea where you stood. It now stops after a set time and tells you
Your settings page now tells you the date a subscription ends, before it does.
- —If your subscription was scheduled to end, Settings could still show it as renewing — so the first sign anything had changed was your copying stopping. It now says "Cancels" with the actual date, and the notice clears the moment you reactivate
You can switch Google accounts again after signing out.
- —Signing out and choosing "Continue with Google" put you straight back into the same account without asking which one you wanted. Google now always offers the account picker, so switching accounts works
Eight new guides, including honest comparisons with the other copiers people weigh us against.
- —Comparison guides for the three alternatives people actually weigh us against — they say plainly where the other tool is cheaper or better suited, because a comparison that never loses is not worth reading
- —Guides on running several evaluations at once, what decides whether copying is permitted on a funded account, and how a prop account differs from a personal one
- —A guide on copier latency that refuses to quote a millisecond figure, because the number that decides your fill is your broker's execution and no copier controls it
- —A troubleshooting guide for when a trade does not copy, covering the six causes it usually is — including the MetaTrader investor password, which connects fine and can never place an order
You can now remove an archived or deleted account from a repeater.
- —An archived or deleted account stayed listed on its repeater with no direct way to take it off. You can now untick it — it stays on screen, marked as removing, until you save. If you change your mind, close without saving
- —Each guide now ends with the guides most related to it, so you can follow a topic through instead of going back to the index every time
A copied position could keep showing as open after your broker had already closed it. Fixed, along with the alert that should have told you.
- —If your broker closed a copied position while Trepeat's connection to it was disrupted, the trade could keep showing as open — sometimes for hours — even though your account was flat. Trepeat now takes the broker's word for it and closes the trade out
- —In that situation you weren't told anything. A copy that's left open when its source has closed now raises an alert, even when the connection is the thing that's misbehaving
- —A disrupted connection could stay disrupted instead of resetting itself, if the way it was failing changed while it was recovering
- —Trepeat could email you to close a position by hand that your broker had already closed
- —The control for hiding account numbers now sits next to the account number itself, and works on phones and tablets — previously it only existed in the desktop table, and covered one list at a time. One switch now covers your active, archived and deleted accounts
Four fixes to how pages load — a flashing cookie notice, sections that started out blank, mobile screenshots showing the desktop layout, and being asked about cookies on every subdomain.
- —The cookie notice briefly appeared and vanished on every page load, even after you'd already made your choice. It now stays hidden once you've chosen
- —On the public site, everything below the top of the page could start out blank and only appear a moment later. Those sections are now visible as soon as the page arrives
- —On phones and tablets, the product screenshots briefly showed the desktop layout before switching, nudging the rest of the page as they did. They now show your device's layout straight away
- —The cookie notice asked again each time you moved between the main site, the app, and the admin area. Your choice now carries across all three, so you're asked once
Pages could show an error screen instead of loading. Fixed at the source, plus the app now recovers on its own.
- —Pages could show an error screen instead of loading. A few of the app's own files were being requested from the wrong address, so browsers refused them — they now load correctly
- —Separately: if you open a page while an update is going out, the app refreshes itself once and carries on instead of showing an error. Nothing is lost, and no action is needed
Alerts about a copy that didn't place now explain what went wrong in plain language.
- —When a copy can't be placed, the alert now says what actually happened — the market closed at your broker, not enough free margin, an order size your broker wouldn't accept — instead of quoting an internal error string
- —If your broker returns something we don't have plain wording for, the alert now attributes it to your broker rather than presenting it as ours, so you know where the message came from and who to ask
Copy sizing now follows each follower broker's own volume rules, plus mobile and search fixes.
- —Copy volume follows each follower broker's own limits — lot step, minimum and maximum per order. Brokers differ on the same symbol, and it's the follower's rules that decide whether an order is accepted, so those are the ones we size to
- —You're told when a broker's per-order ceiling makes a copy smaller than your sizing asked for — that follower position gains and loses less than the source, which is worth knowing rather than discovering later
- —Copies on symbols with larger minimums or maximums — several crypto and index CFDs — could be refused by the follower's broker and silently not placed
- —Typing quickly into any search box could drop or reorder characters
- —Dialogs on phones stretched edge to edge with square corners; they're now centred cards
Trepeat is live — sign-ups are open. Earlier versions were pre-launch development builds.
- —MetaTrader 4 & 5 integration via MetaAPI — real-time WebSocket trade stream on demo-server accounts (prop-firm evaluation and funded included); live real-capital accounts aren't supported for now
- —Multi-follower repeaters with per-repeater risk controls — multiplier / equity-ratio sizing, max-volume cap, symbol allowlist, and symbol remapping; pause any follower independently
- —Real-time copy engine with live floating P&L per repeater and per account, a reconnect sweep that closes copies whose source has already closed, and magic-filter safety (never touches your manual trades)
- —Encrypted credential vault (AEAD) + two-factor authentication with recovery codes
- —Stripe billing — Starter, Growth, and Scale plans plus pre-paid extra account slots
- —Plus a trade journal with P&L calendar, real-time alerts, a full execution audit trail, the live monitoring dashboard, and a dark trading-terminal UI.