Custom domain api.digifoodly.io (project 'digifoodly', service 'backend') has been stuck with certificate status VALIDATING_OWNERSHIP and verified=false for about 2 hours after adding the required DNS records.

DNS is correctly configured and propagated:

• CNAME api.digifoodly.io -> 00ikct9b.up.railway.app (confirmed via public DNS; Railway's own domain-status API also reports this record as PROPAGATED)
• • TXT _railway-verify.api.digifoodly.io -> railway-verify=98a1fa119f56e8db6a5612d6ada012a50b40cc433fe2f5253e4185ce214b82c2 (added and publicly propagated since ~2026-09-16 21:57 UTC)

No CAA records block Let's Encrypt, and DNSSEC is not enabled on the domain. HTTPS requests to the domain still return Railway's generic *.up.railway.app wildcard certificate instead of a dedicated one.

Additional context: this domain was originally added around 2026-09-10, and there was a stale 'staged change' for it sitting in the project's pending changes for about a week. I accepted that staged change on 2026-09-16, which is what caused the TXT requirement to appear for the first time. It's possible the domain's verification state has been stuck/corrupted since that original add.

Project ID: 72ef6828-9d05-409c-83e1-f070e6caa308

Service ID: 99a1ee00-e8cb-4c68-b755-31aab3a83241

Domain ID: 36c44fce-2870-4645-9457-e7a9bf100c20

Could you please check why verification isn't completing, or manually retrigger it? Thanks!