Grace rule

Studio roles: "Owner", "Administrator" and "Community manager" see members on grace in the members directory.

An external register can be down for a while, for example during maintenance of the HR system. The grace rule keeps your members signing in meanwhile.

The rule

While a register is unavailable, a member whose last valid check is less than 7 days old keeps signing in on that last result, in the communities of that result. Everyone else waits, and so does every onboarding: they see that they should try again later.

The check itself is still logged as "Unavailable", with the reason "A register could not answer".

What you see

• Members directory: the status "Valid, on grace", with the hint "The register could not answer at the last check; the last valid check counts for 7 days".
• After 7 days without a valid check: "Not valid: register unavailable, grace expired". The next valid check makes the membership valid again.
• Check lookup: the login check shows "Unavailable" and the register reached.

The same 7 days apply between sign-ins: a frontend may treat a signed-in person as a member only while their last valid check is less than 7 days old.

An example

At the last sign-in of Sabrina Koller (PQ-30544) at the Pannoniqa App, SAP HR did not answer. Her last valid check was a day before, so she signed in as a member, and the members directory shows her as "Valid, on grace".

What to do

1. Open the register and test its connection. The test names the cause, for example "no answer within 5 seconds".
2. Ask your IT to fix the register within the 7 days.
3. Check the register activity for a recent change to the connection, such as a new base URL that removed the API key.