Notification sending error

 

Hello,

Please help me figure out what the issue is — both I and my client, for whom I am developing a trading robot, are experiencing a notification sending error: send request failed (raw - read failed, 0 wsa error, 1 bytes needed).

Sometimes this error occurs, and sometimes it does not, and the notification is delivered successfully.

The SendNotification function always returns true.

This issue occasionally appears not only when sending notifications from the EA, but also when pressing the “Test” button in the terminal’s notification settings.

Thank you in advance!

Files:
 
Tatiana Zyrianova:

Hello,

Please help me figure out what the issue is — both I and my client, for whom I am developing a trading robot, are experiencing a notification sending error: send request failed (raw - read failed, 0 wsa error, 1 bytes needed).

Sometimes this error occurs, and sometimes it does not, and the notification is delivered successfully.

The SendNotification function always returns true.

This issue occasionally appears not only when sending notifications from the EA, but also when pressing the “Test” button in the terminal’s notification settings.

Thank you in advance!

"Strict use restrictions are set for the SendNotification() function: no more than 2 calls per second and not more than 10 calls per minute. Monitoring the frequency of use is dynamic. The function can be disabled in case of the restriction violation" (https://www.mql5.com/en/docs/network/sendnotification).

As you're developing a trading robot, rapid and repeated testing could have caused an unintended consequence. If this is the case, only the Service Desk can help.

 
Ryan L Johnson #:

"Strict use restrictions are set for the SendNotification() function: no more than 2 calls per second and not more than 10 calls per minute. Monitoring the frequency of use is dynamic. The function can be disabled in case of the restriction violation" (https://www.mql5.com/en/docs/network/sendnotification).

As you're developing a trading robot, rapid and repeated testing could have caused an unintended consequence. If this is the case, only the Service Desk can help.

Yes, I also thought that I might have violated this rule.

But the thing is, sometimes the notifications are sent, and sometimes they are not.

If the error is indeed caused by violating the rule, I will contact the Service Desk.

Thank you for your help!

 
Tatiana Zyrianova #:

Yes, I also thought that I might have violated this rule.

But the thing is, sometimes the notifications are sent, and sometimes they are not.

If the error is indeed caused by violating the rule, I will contact the Service Desk.

Thank you for your help!

You're most welcome.

Frankly, "Monitoring the frequency of use is dynamic" is a bit vague. Perhaps that suggests on again/off again on a rolling basis.