How to easily identify the respective account for a running cBot ?

PanagiotisCharalampous
03 Jul 2024, 07:30

Hi there,

This is the case even when a cBot is running (as shown below), suggesting that the respective cBot instance is always running on the active account, which is (obviously) not always the case.

I do not understand what is the problem. What other case could there be for local execution?

In addition to this, I don't see any explicit reference to the respective account where a cBot is running.

What do you mean by explicit reference?

ncel01
03 Jul 2024, 13:03

RE: How to easily identify the respective account for a running cBot ?

PanagiotisCharalampous said: 

Hi there,

This is the case even when a cBot is running (as shown below), suggesting that the respective cBot instance is always running on the active account, which is (obviously) not always the case.

I do not understand what is the problem. What other case could there be for local execution?

In addition to this, I don't see any explicit reference to the respective account where a cBot is running.

What do you mean by explicit reference?

Hi Panagiotis,

I do not understand what is the problem. What other case could there be for local execution?

Isn't the issue obvious? I've addressed this in the original thread.
The account mentioned in the screenshot is not the account in which the cBot is running.
Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?

What do you mean by explicit reference?

Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.

 

PanagiotisCharalampous
04 Jul 2024, 04:36

RE: RE: How to easily identify the respective account for a running cBot ?

ncel01 said: 

PanagiotisCharalampous said: 

Hi there,

This is the case even when a cBot is running (as shown below), suggesting that the respective cBot instance is always running on the active account, which is (obviously) not always the case.

I do not understand what is the problem. What other case could there be for local execution?

In addition to this, I don't see any explicit reference to the respective account where a cBot is running.

What do you mean by explicit reference?

 

Hi Panagiotis,

I do not understand what is the problem. What other case could there be for local execution?

Isn't the issue obvious? I've addressed this in the original thread.
The account mentioned in the screenshot is not the account in which the cBot is running.
Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?

What do you mean by explicit reference?

Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.

 

Hi ncel01,

I still don't understand

Isn't the issue obvious? I've addressed this in the original thread.

No, that is why I am asking. 

The account mentioned in the screenshot is not the account in which the cBot is running.

Please provide screenshots demonstrating this

Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?

Cloud execution. If the cBot is executed on the cloud it could run on a different account.

Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.

I don't understand what do you want to check. It should be what you see on your screen.

Best regards,

Panagiotis

ncel01
04 Jul 2024, 17:41 ( Updated at: 04 Jul 2024, 19:55 )

RE: RE: RE: How to easily identify the respective account for a running cBot ?

PanagiotisCharalampous said: 

ncel01 said: 

PanagiotisCharalampous said: 

Hi there,

This is the case even when a cBot is running (as shown below), suggesting that the respective cBot instance is always running on the active account, which is (obviously) not always the case.

I do not understand what is the problem. What other case could there be for local execution?

In addition to this, I don't see any explicit reference to the respective account where a cBot is running.

What do you mean by explicit reference?

 

Hi Panagiotis,

I do not understand what is the problem. What other case could there be for local execution?

Isn't the issue obvious? I've addressed this in the original thread.
The account mentioned in the screenshot is not the account in which the cBot is running.
Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?

What do you mean by explicit reference?

Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.

 

Hi ncel01,

I still don't understand

Isn't the issue obvious? I've addressed this in the original thread.

No, that is why I am asking. 

The account mentioned in the screenshot is not the account in which the cBot is running.

Please provide screenshots demonstrating this

Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?

Cloud execution. If the cBot is executed on the cloud it could run on a different account.

Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.

I don't understand what do you want to check. It should be what you see on your screen.

Best regards,

Panagiotis

Hi Panagiotis,

The account mentioned in the screenshot is not the account in which the cBot is running.
Correction: Every time a new account is selected, the cBot execution is stopped on the previous account and applied to the new account instantly, which is also not great, I'd say.

However, I noticed that every time a demo account is involved, the cBot execution is stopped and not applied to the new account.
This does not make much sense to me. Shouldn't this work the other way around, for obvious reasons?
To make it worse, users are not warned when switching accounts while a cBot is running, which would prevent a cBot from stopping on the current account, as well as any accidental cBot execution on the new account.

Cloud execution. If the cBot is executed on the cloud it could run on a different account.

Why is this not possible locally as well? It would be a great feature.
At the moment, every cBot running on a different account requires a dedicated cTrader instance which is very resource-intensive.

PanagiotisCharalampous
05 Jul 2024, 05:04

RE: RE: RE: RE: How to easily identify the respective account for a running cBot ?

ncel01 said: 

PanagiotisCharalampous said: 

ncel01 said: 

PanagiotisCharalampous said: 

Hi there,

This is the case even when a cBot is running (as shown below), suggesting that the respective cBot instance is always running on the active account, which is (obviously) not always the case.

I do not understand what is the problem. What other case could there be for local execution?

In addition to this, I don't see any explicit reference to the respective account where a cBot is running.

What do you mean by explicit reference?

 

Hi Panagiotis,

I do not understand what is the problem. What other case could there be for local execution?

Isn't the issue obvious? I've addressed this in the original thread.
The account mentioned in the screenshot is not the account in which the cBot is running.
Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?

What do you mean by explicit reference?

Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.

 

Hi ncel01,

I still don't understand

Isn't the issue obvious? I've addressed this in the original thread.

No, that is why I am asking. 

The account mentioned in the screenshot is not the account in which the cBot is running.

Please provide screenshots demonstrating this

Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?

Cloud execution. If the cBot is executed on the cloud it could run on a different account.

Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.

I don't understand what do you want to check. It should be what you see on your screen.

Best regards,

Panagiotis

Hi Panagiotis,

The account mentioned in the screenshot is not the account in which the cBot is running.
Correction: Every time a new account is selected, the cBot execution is stopped on the previous account and applied to the new account instantly, which is also not great, I'd say.

However, I noticed that every time a demo account is involved, the cBot execution is stopped and not applied to the new account.
This does not make much sense to me. Shouldn't this work the other way around, for obvious reasons?
To make it worse, users are not warned when switching accounts while a cBot is running, which would prevent a cBot from stopping on the current account, as well as any accidental cBot execution on the new account.

Cloud execution. If the cBot is executed on the cloud it could run on a different account.

Why is this not possible locally as well? It would be a great feature.
At the moment, every cBot running on a different account requires a dedicated cTrader instance which is very resource-intensive.

Hi there,

Ok it's more clear now. I still don't see the problem. Local execution works the same way since cAlgo 1.0. Running a cBot on an account that is not the one to which cTrader is connected is not as simple as it sounds and not as obvious as it might be for your. Not all users would like such a breaking change to the way cTrader has always worked. That's why you have an option of running your cBot in an external process.

Best regards,

Panagiotis

ncel01
05 Jul 2024, 06:28

RE: RE: RE: RE: RE: How to easily identify the respective account for a running cBot ?

PanagiotisCharalampous said: 

ncel01 said: 

PanagiotisCharalampous said: 

ncel01 said: 

PanagiotisCharalampous said: 

Hi there,

This is the case even when a cBot is running (as shown below), suggesting that the respective cBot instance is always running on the active account, which is (obviously) not always the case.

I do not understand what is the problem. What other case could there be for local execution?

In addition to this, I don't see any explicit reference to the respective account where a cBot is running.

What do you mean by explicit reference?

 

Hi Panagiotis,

I do not understand what is the problem. What other case could there be for local execution?

Isn't the issue obvious? I've addressed this in the original thread.
The account mentioned in the screenshot is not the account in which the cBot is running.
Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?

What do you mean by explicit reference?

Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.

 

Hi ncel01,

I still don't understand

Isn't the issue obvious? I've addressed this in the original thread.

No, that is why I am asking. 

The account mentioned in the screenshot is not the account in which the cBot is running.

Please provide screenshots demonstrating this

Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?

Cloud execution. If the cBot is executed on the cloud it could run on a different account.

Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.

I don't understand what do you want to check. It should be what you see on your screen.

Best regards,

Panagiotis

Hi Panagiotis,

The account mentioned in the screenshot is not the account in which the cBot is running.
Correction: Every time a new account is selected, the cBot execution is stopped on the previous account and applied to the new account instantly, which is also not great, I'd say.

However, I noticed that every time a demo account is involved, the cBot execution is stopped and not applied to the new account.
This does not make much sense to me. Shouldn't this work the other way around, for obvious reasons?
To make it worse, users are not warned when switching accounts while a cBot is running, which would prevent a cBot from stopping on the current account, as well as any accidental cBot execution on the new account.

Cloud execution. If the cBot is executed on the cloud it could run on a different account.

Why is this not possible locally as well? It would be a great feature.
At the moment, every cBot running on a different account requires a dedicated cTrader instance which is very resource-intensive.

Hi there,

Ok it's more clear now. I still don't see the problem. Local execution works the same way since cAlgo 1.0. Running a cBot on an account that is not the one to which cTrader is connected is not as simple as it sounds and not as obvious as it might be for your. Not all users would like such a breaking change to the way cTrader has always worked. That's why you have an option of running your cBot in an external process.

Best regards,

Panagiotis

Panagiotis,

That's clear. Thanks!

Any comments on the following?

I noticed that every time a demo account is involved, the cBot execution is stopped and not applied to the new account.
This does not make much sense to me. Shouldn't this work the other way around, for obvious reasons?
To make it worse, users are not warned when switching accounts while a cBot is running, which would prevent a cBot from stopping on the current account, as well as any accidental cBot execution on the new account.