[389-users] sd_notify called before 389-ds really ready?

I have a service on my 389-ds host that is configured in systemd to depend on 389-ds and
start after dirsrv.target.  However, unless I add a sleep (ExecStartPre systemd stanza) to
the startup of that other service it fails to start as 389 is not fully ready.  I can see
that systemd is respecting the dependencies, but the client starts before 389 is able to
accept its connection.

389-ds appears to use the notify systemd service type.  Is it possible that sd_notify is
being called before the services are truly ready to accept client connections?