Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" is a real answer.
1
In plain terms. Western Slope's AppFolio connection has been silently failing some guest-card updates and rent-roll reads for weeks, because one of our two login-health checks keeps coming back unsure. Should we force a brand-new login for that AppFolio account to try to clear it, or hold off and have someone check the session directly first, since a forced login risks AppFolio temporarily locking the account if that wasn't actually the problem?
The full question, as raised
Western Slope's AppFolio session keeps coming back 'ambiguous' on one of our two health checks (the account-wide API check says the login is fine; a second, newer check that loads one property page does not), and that single ambiguous reading has been quietly blocking guest-card writes, showings and rent-roll reads for this customer for weeks. Should someone force a brand-new AppFolio login for this account to try to clear it, or hold off and check the Browserbase session directly first, since forcing a login risks AppFolio temporarily locking the account out if the login wasn't actually the problem?
Why, and what was tried
The session raising this recommends: Hold off — check the Browserbase session directly first The account-wide login check already says the session is fine; only the newer, narrower page-load check is ambiguous, so forcing a brand-new login risks an AppFolio lockout without fixing anything if the real bug is in how we read that second check. Tried first, unsuccessfully: Checked the open-decisions board and this week's alert history for this account/error first — nothing already tracked this exact question. Then read the actual Sentry error history (several related issues going back to Sept 13) and the browser-agent's session-probe code to see exactly which of the two checks was failing and why, rather than guessing.