A request to reauthorise means the permission granted to read the data has reached the end of its term.
Why it happens on a schedule
Banks and accounting providers grant access for a fixed period and require the customer to confirm it again when that period ends. The length is set by the institution, and in some regions it is a regulatory requirement rather than a provider's choice.
So a periodic request is the system working as the institution designed it.
What reconnecting does
Confirms consent using the existing connection. It does not create a second one, and history already collected stays where it is.
Data resumes from where it stopped, so a short gap fills in once the connection is confirmed.
What triggers it earlier than the schedule
A password changed at the bank.
Access revoked from the bank's own security settings, which sometimes happens when a customer reviews connected applications.
A new security requirement introduced by the institution.
Multi-factor settings changed on the banking login.
Where it is done
Sources lists every connection with its status, and reconnection starts from there — see bank connection.
Doing it promptly
Data is not collected between the request and the confirmation, and the gap is filled on reconnection. The longer the gap, the longer the figures reflect an earlier position — see a connection stopped bringing data in.
Credentials
Reconnection happens with the institution rather than with Omnyra, and banking credentials are entered on the institution's own screen — see bank connection.