Hello,
Thanks for contacting us and sorry for any inconvenience that might have been caused due to that.
I wasn’t able to replicate the issue on my end. I also wasn’t able to find any ticket with a similar issue. We might need to take a closer look at the settings. Please edit the first post on this ticket and include your WordPress logins in the designated Sensitive Data section.
Please do take a complete backup of your website before sharing the information with us.

It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:
https://wordpress.org/plugins/temporary-login-without-password/
You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):
https://wordpress.org/plugins/wp-security-audit-log/
We really look forward to helping you.
I think i missed one point in describing the problem. Let’s us understand this with an example:
For example, today, on 11th Feb i created a job posting schema for a recruitment and the last date to apply for the job is 15th Feb, let’s suppose. Now, in place of job publishing date i have filled, today’s date and for the job expiry date i have put 15th Feb 2022 as per standard date format and all…
and in this tab which says: “Unpublish when expired”, i have selected “NO”….so, technically this post should not go to draft on/after expiry date.
Now, when the date comes to 15 th Feb, 80-90% chances are that this job posting post will go to draft….when i open it and see the schema…it is saying “YES” in the tab : “Unpublish when expired”
THOUGH, we had selected to ‘NO’ but it was converted into a YES by its own….then i will have to select again “NO” in place of the tab which says “Unpublish when expired” . After doing that we have to publish it again….and …now the “NO” stays there unless untill we modify it again in future……
This bug makes us feel cheated 🙂 because unlike to what it says it does the just opposite …promise broken 🙂
This bug makes us face a lot of 404 issues….it makes us go through the schema and select the required option and then Publish it again!!
You can understand the situation. And, i assure you that i am not alone who is facing this, perhaps hundreds of people….it is different thing that they have never tried to report it …they have left it to you that, in future you guys will correct it….
Hello,
I had tried this on my end and wasn’t able to replicate the issue. If you want us to check this further then please provide the login details of your site so we can check why you are facing the issue.
Looking forward to helping you.
Thanks.
Hello,
I have updated the sensitive data as requested. Can you please check further?
Thank you.
Hello,
I tried to log in to your site but it is returning an error:

Please check and let us know when we can log in.
Looking forward to helping you.
Thanks.
Please use the login url correctly….i have changed wp-admin for login page….so, use the full login url and try again….
Please use login url correctly, this is different from the default wp login page
Hello,
We would like to further debug this issue over your admin dashboard but it seems the access you shared is so limited at the moment. Could you please elevate the access to the admin level so we can access some of the settings pages like the Rank Math settings and the list of plugins as we might suspect some plugin conflicts?
We are looking forward to helping you.
Hello,
Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.
If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
Thank you.