Answered
Can confirm now here it's fixed too.
Hi andrey_0108 and Synergist5EB8,
Thank you for confirming the fix. This behavior was caused by a backend issue, which was resolved on the same day you mentioned.
Please don't hesitate to let us know if we can help.
Thanks,
Meenakshi
Sign up
Already have an account? Login
To post, reply, or follow discussions, please sign in with your Adobe ID.
Sign inSign in to Adobe Community
To post, reply, or follow discussions, please sign in with your Adobe ID.
Sign inEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
