In cloud, Account.UserId and Account.Number is 0. Account.BrokerName also wrong. Account.UserNickName property is not available.
In cloud, Account.UserId and Account.Number is 0. Account.BrokerName also wrong. Account.UserNickName property is not available.
07 Oct 2024, 03:13
Please note that I am using different cTrader ID to post in this forum. Not the same as the one I run cBot.
My broker: Tradona Markets.
Tradona Markets CTrader version: 5.0.38.32115.
Sample source codes that reproduce the issues:
using System;
using cAlgo.API;
using cAlgo.API.Collections;
using cAlgo.API.Indicators;
using cAlgo.API.Internals;
namespace cAlgo.Robots
{
[Robot(AccessRights = AccessRights.None, AddIndicators = true)]
public class Testing : Robot
{
protected override void OnStart()
{
// To learn more about cTrader Automate visit our Help Center:
// https://help.ctrader.com/ctrader-automate
Print($"User ID: {Account.UserId}");
Print($"Account number: {Account.Number}");
Print($"User nick: {Account.UserNickName}");
Print($"Broker: {Account.BrokerName}");
}
protected override void OnTick()
{
// Handle price updates here
}
protected override void OnStop()
{
// Handle cBot stop here
}
}
}
Source codes above produce the following output:
07/10/2024 03:10:46.366 Info | Account number: 0
07/10/2024 03:10:46.366 Error | Account.UserNickName property is not available for Cloud cBots
07/10/2024 03:10:46.366 Info | User nick:
07/10/2024 03:10:46.366 Info | Broker: Spotware
07/10/2024 03:10:46.366 Info | User ID: 0
07/10/2024 03:10:44.586 Info | CBot instance [5792547e-04f4-4c7b-bbe8-80d908c39c2d, XAUUSD, h1] started.
07/10/2024 03:10:44.244 Starting cBot...
As you can see, both the Account.UserId and Account.Number is 0, which is wrong. Broker also wrong. My broker is Tradona Market, not Spotware. Account.UserNickName property also not available.
I really need the Account.UserId and Account.Number information. Please fix this issue ASAP.
Replies
ncel01
13 Oct 2024, 16:44
( Updated at: 14 Oct 2024, 05:07 )
I don't really get why this is taking so long to be fixed.
Although this has been communicated as solved already 3 month ago (here below), the issue still remains:
https://ctrader.com/forum/announcements/44366/
@ncel01
PanagiotisCharalampous
07 Oct 2024, 06:08
Hi there,
It's a known issue and will be fixed in an upcoming update.
Best regards,
Panagiotis
@PanagiotisCharalampous