Non-standard call signs are not entered into the log

[MikleBas]

Today I made a QSO, both with non-standard call signs

1. 4U29MAY
2. D1IY
   And both times, when I pressed the Save button, nothing happened, is it just me (and this is a local glitch of my server) or someone try entering these call signs into the communication window, will they be recorded in the log?
   Thank you

PS magazine version v2.6.0
all communications were carried out in CW mode

[magicbug]

If you update Country File 1. should go in without a problem else manually select the dxcc.

2. isn't a valid callsign.

[MikleBas]

1. Updated the files, it helped (although the crown requires auto-update)
   Thank you!

[MikleBas]

p. 2 The time will come for these regions of Russia to be recognized, or not, but this is already politics, it has no place in Radio yet.. ;)

[magicbug]

I'm not refering to politics its a prefix that hasn't been issued by the ITU simple as that.

[MikleBas]

Ok!

[R1BLH]

p. 2 The time will come for these regions of Russia to be recognized, or not, but this is already politics, it has no place in Radio yet.. ;)

Previous versions of the Cloudlog were able to log QSOs with such callsigns without problems:
Digi mode QSO, last logged on 08.04.2024 in my log via the Gridtracker.
SSB mode QSO, last logged on 11/04/2022 in my log manually.

Now (v.2.6.13) manual logging is blocked. API logging need to be checked.