Adding to @Alberto_Umana questions, this seems like an ephemeral token/session issue or a race condition or maybe a network/private link glitch. I'd suggest increasing the log verbosity and capture detailed logs to compare successful vs failed runs, ensure that the service principal or job user is consistently recognized. If this still doesn't help with isolating the root cause, please raise a support ticket with out Databricks Support team for deeper analysis.