ACME fail No ACME certificate generation required for domains

Hi,
I have a wildcard certificate for *.domain.de and when trying to add apps.domain.de cert it tells me that "No CAME cert generation required", is it because it finds a suitable certificate for that domain? What will happen when the *.domain.de expires? will it automatically trigger the generation of the new cert?
I don't plan to renew the wildcard cert but I would like to start moving the services to a individual domain certificates.

time="2022-11-07T13:22:55Z" level=debug msg="Try to challenge certificate for domain [apps.domain.de] found in HostSNI rule" rule="Host(`apps.domain.de`) && PathPrefix(`/pptop`)" providerName=sectigo.acme ACME CA="https://acme.sectigo.com/v2/OV" routerName=savitski-group-pptop-shiny-apps-embl-de-pptop@kubernetes
time="2022-11-07T13:22:55Z" level=debug msg="Try to challenge certificate for domain [apps.domain.de] found in HostSNI rule" ACME CA="https://acme.sectigo.com/v2/OV" routerName=websecure-savitski-group-pptop-shiny-apps-embl-de-pptop@kubernetes rule="Host(`apps.domain.de`) && PathPrefix(`/pptop`)" providerName=sectigo.acme
time="2022-11-07T13:22:55Z" level=debug msg="Looking for provided certificate(s) to validate [\"apps.domain.de\"]..." providerName=sectigo.acme ACME CA="https://acme.sectigo.com/v2/OV" routerName=arendt-group-evocelldb-apps-embl-de-evocelldb@kubernetes rule="Host(`apps.domain.de`) && PathPrefix(`/evocelldb`)"
time="2022-11-07T13:22:55Z" level=debug msg="No ACME certificate generation required for domains [\"apps.domain.de\"]." rule="Host(`apps.domain.de`) && PathPrefix(`/evocelldb`)" providerName=sectigo.acme ACME CA="https://acme.sectigo.com/v2/OV" routerName=arendt-group-evocelldb-apps-embl-de-evocelldb@kubernetes

„No cert generation required“ usually happens when all required certs already exist in acme.json.

From the docs:

Traefik automatically tracks the expiry date of ACME certificates it generates.
By default, Traefik manages 90 days certificates, and starts to renew certificates 30 days before their expiry.

Thanks!
The thing is that the wildcard certificate wasn't generated via ACME, was manually requested and mounted inside the container...but it seems to find that is existing already a certificate that fits the domain.
Cheers.