The "Record not found" error usually means there's a mismatch between the account type and the contact's role. An advisor account can’t see another advisor’s trips or authorizations. Make sure the account type matches the user’s role in Tern; switching between a traveler and advisor account often resolves this error. Always ensure correct email and account details, and verify your client has the right type of access in the system. You got this! If you need help sorting this out, our support team is here for you.
Written by David Shull
Updated this week