Hi all
We're experiencing some issues with our Demo environment right now, so you might find the following errors:
- Missing markets/EPICs
- Some positions not showing
- Streaming balance issues
We're looking into this, and will provide updates here. Sorry for any inconvenience this has caused.
Chris
© 2003-2020
Spread bets and CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage. XX% of retail investor accounts lose money when trading spread bets and CFDs with this provider. You should consider whether you understand how spread bets and CFDs work, and whether you can afford to take the high risk of losing your money. Professional clients can lose more than they deposit. Spread bets and CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage.
Hi Chris,
do you have any schedule for working on it?
Since yesterday I'm still receiving a 500 error when I try to open a limit order
Thanks in advance
Massimo
We're also wondering when it's going to be fixed. We can't even open or close positions.
I didn't post yesterday because I figured it will be fixed when it's fixed. But I'm now worried we might be in for the long run..
Hi Chris,
Can we have an update for the recovery of the demo API/stream ? So far the demo stream server seems to push a few indices but no sign of FX or commodities at all. As i already mentioned to the IG phone support yesterday, this is really annoying for me since i have some algos coming right from backtests that need to be tested in demo mode.
Thanks for your diligent answer,
Clément Gamé.
My bad, prices push issues were on my side because of a misconf of my LS client. things seem to be back to normal.
Hello,the issues within demo accounts seems not be solved at the moment. Still unable to send orders by API or with the Java applications on the site. Could not retrieve all items in the market. Do you have an ETA on the fixes ? Thank you.
Hi any news ?
On my side I've got problem with the stream flows (demo or prod)
And lot of my user still have problem with the Login phase ...
What's going on ????
Hi both,
We were experiencing issues with our Platform yesterday evening, however trading issues were resolved soon after, and watchlists have now been restored.
Can you confirm what issues you are continuing to encounter, and send any specific details via the Contact Us page.
Thanks,
Chris
Hi Chris,
for me demo platform is still with issues. Cannot put working orders that worked before(and haven't modified my code). They're rejected. As a example, you can have a look at dealReferences 4Q9ZC4DZLG4WM2J,4Q9ZC4DZLG4VX8U or 4Q9ZC4DZLG4HDU7, in my demo account past activity (account demo-spartakkus)
Thanks!
For more details, over your API companion, demo environment, I put a working order and get HTTP 200 success. Then I click get working orders and the list is empty
any update on the issue over demo platform? Working orders still affected
Thanks
Hi,
Got :
Error encountered !
Status code: 500
Error code: system.error
and if i dont get this message, orders are rejected though...
Hello,
Less bug/issue from last friday, but, and ther is a But, the stream flows seems to be not so efficient has I expected.
I've correct my code (several mistake on my side also).
No more major issue know.
I'm still getting an "Incorrect instrument setup" error for demo accounts when trying to get a subscription with the streaming API. The same setup works fine for live accounts. I wonder when the demo API issues might get fixed.
Great. Looks like this is working again.
Using the /marketnavigation API query to drill down to the Sprint Markets I get very different results between Live and Demo accounts. The final list for Live returns 23 EPICS (including 8 currency pairs), while Demo returns 39 EPICS (including 12 currency pairs). I'm wondering if we can have an update on IG's intention here?
Live account:
id: '357975'
name: 'NEW - Sprint Markets'
id: '381908'
name: 'All Sprint Markets'
id: '381909'
name: 'All instruments'
EPIC
'FM.D.EURUSD24.EURUSD24.IP'
'FM.D.DOW.DOW.IP'
'FM.D.FTSE.FTSE.IP'
'FM.D.DAX.DAX.IP'
'FM.D.GBPUSD24.GBPUSD24.IP'
'FM.D.USDJPY24.USDJPY24.IP'
'FM.D.EURJPY24.EURJPY24.IP'
'FM.D.GBPJPY24.GBPJPY24.IP'
'FM.D.AUDUSD24.AUDUSD24.IP'
'FM.D.OIL.OIL.IP'
'FM.D.GOLD.GOLD.IP'
'FM.D.USDCAD24.USDCAD24.IP'
'FM.D.NIKKEI.NIKKEI.IP'
'FM.D.USDCHF24.USDCHF24.IP'
'FM.D.ASX.ASX.IP'
'FM.D.BITCOIN.BITCOIN.IP'
'FM.D.CAC.CAC.IP'
'FM.D.MIB.MIB.IP'
'FM.D.IBEX.IBEX.IP'
'FM.D.OMX.OMX.IP'
'FM.D.SMI.SMI.IP'
'FM.D.TASE.TASE.IP'
'FM.D.TAD.TAD.IP'
Demo account:
id: '278544'
name: 'Sprint Markets'
id: '302307'
name: 'All Sprint Markets'
id: '302308'
name: 'All instruments'
EPIC
'FM.D.AUDJPY24.AUDJPY24.IP'
'FM.D.AUDUSD24.AUDUSD24.IP'
'FM.D.ASX.ASX.IP'
'FM.D.ASX24.ASX24.IP'
'FM.D.BITCOIN.BITCOIN.IP'
'FM.D.China300.China300.IP'
'FM.D.DOW24.DOW24.IP'
'FM.D.EURGBP24.EURGBP24.IP'
'FM.D.EURJPY24.EURJPY24.IP'
'FM.D.EURUSD24.EURUSD24.IP'
'FM.D.ChinaA50.ChinaA50.IP'
'FM.D.TEST.TEST.IP'
'FM.D.FTSE.FTSE.IP'
'FM.D.CAC.CAC.IP'
'FM.D.DAX24.DAX24.IP'
'FM.D.Topix.Topix.IP'
'FM.D.NAS24.NAS24.IP'
'FM.D.GBPJPY24.GBPJPY24.IP'
'FM.D.GBPUSD24.GBPUSD24.IP'
'FM.D.DAX.DAX.IP'
'FM.D.GOLD.GOLD.IP'
'FM.D.Nifty50.Nifty50.IP'
'FM.D.NIKKEI.NIKKEI.IP'
'FM.D.Nikkei24.Nikkei24.IP'
'FM.D.AEX.AEX.IP'
'FM.D.Silver24.Silver24.IP'
'FM.D.SGX.SGX.IP'
'FM.D.IBEX.IBEX.IP'
'FM.D.OMX.OMX.IP'
'FM.D.SMI.SMI.IP'
'FM.D.SNP.SNP.IP'
'FM.D.SNP24.SNP24.IP'
'FM.D.OIL.OIL.IP'
'FM.D.USDCAD24.USDCAD24.IP'
'FM.D.USDCHF24.USDCHF24.IP'
'FM.D.USDJPY24.USDJPY24.IP'
'FM.D.DOW.DOW.IP'
'FM.D.TASE.TASE.IP'
'FM.D.TAD.TAD.IP'
Hi Neilcaithness,
There are differences between the two environments, and they have been setup with different instruments in the hierarchy. We'll see if we are able to amend this configuration.
Thanks,
Chris
I opened a position last night that by now has moved several points past its stopLevel but has not been closed. Does anyone else have problems with stoplosses that do not execute properly?
Hi,
During my debug session, I was set a STOP/LIMIT update position by API (command accepted with Deal reference).
The value was never respect the STOP. In the historic vue, I saw 'Stop too close'.
So, The API command is accepted but server doesn't accept it.
I'm adding a check with the Streaming API to confirm the STOP setting.