Schlage access code mutation delayed if account token requires refresh

[codetheweb]

Prerequisites

• Can this issue be reproduced in a sandbox workspace? No
• Does this issue represent a regression? Did it previously work? No

Description

If /access_codes/update or (/access_code/create) is called for a Schlage access code when the account token is invalid, Seam doesn't immediately attempt to refresh the token, resulting in the access code mutation being delayed until the token is refreshed.

Steps to Reproduce

1. Wait for Schlage account token to become invalid
2. Attempt to create an access code

Expected behavior: access code updates complete quickly

Actual behavior: can take >50m for an access code update to complete

Potential solution

Proactively refresh account tokens.