When an External Integration Is Not Working
Where to check when single sign-on, LINE linking, or API access is not working.
【Before you start】
There is no "Integrations" screen or connection status list in the admin console.
Each integration is checked differently — see below.
【Cannot sign in with single sign-on (SSO)】
· Check whether the SSO button appears on the login page. If not, SSO has not been configured (see #SEC-008)
· Check that the account is active in your IdP (Google Workspace, Microsoft 365, Okta, etc.)
· If you rotated the client secret in your IdP, the WorkVell configuration must be updated too — contact support
· While SSO is unavailable, sign in with your email address and password
【Disaster-safety confirmations are not arriving on LINE】
· Employee side: check that Settings → LINE shows as linked
· Administrator side: check that LINE delivery is enabled and the channel settings are correct (see #GEN-174)
【API calls are failing】
Check according to the error returned.
· 401: the API key is wrong, revoked, or expired
· 403: the source IP address is not on the allowlist, or the key lacks the required scope
· 429: you have exceeded the rate limit — wait and retry (see #GEN-200)
Contact support in any of these cases and we will check the state of the key.
【If the problem persists】
Contact support with the date and time, what you were doing, and the error message.
이 글이 도움이 되었나요?