Kula surfaces a lot of different signals when something isn't working the way you expect — a banner asking you to reconnect an integration, a flow step that stalls, a job board posting that sits "In Progress" longer than expected, or a plain error message with no obvious next step. Most of these aren't bugs. This article walks through what Kula's error and warning signals actually mean, which ones point to something you can fix yourself, and which ones are known product gaps worth reporting rather than troubleshooting on your own.

What "broken" usually means

Integration disconnected or needs reauthentication

This is the single most common thing that looks broken but has a one-click fix.

• Mailbox disconnected. Kula shows a banner reading something close to "Your email integration requires reauthentication," and blocks that user from sending email until they reconnect. If the disconnected mailbox is a flow's sender, the flow can stop sending on that step until it's reconnected.

• Calendar disconnected. A disconnected Google or Outlook calendar stops interview invites from syncing, and self-schedule links belonging to that user will show candidates "No slots available" until the calendar is reconnected — even if the user's actual calendar has open time.

• Zoom token expired or revoked. Org admins now get an email and Slack alert the moment a Zoom token goes invalid, the same way Slack disconnection alerts already worked. The invalid status is visible on the Integrations page, and reconnecting refreshes the Zoom user list immediately instead of waiting for the next daily sync.

• Slack integration shows "Invalid" after reconnecting. If your workspace isn't listed in the Slack app marketplace, Slack requires the reauthentication to be completed by a Workspace Owner — not just a Workspace Admin. If an Admin reconnects instead, Slack silently blocks it and the integration stays marked invalid.

• HRIS integrations (Rippling, TriNet, UKG Pro, and others). A 401 or "permission denied" error is often coming from the HRIS vendor's side rather than Kula — expired credentials, an invalid client ID, or a missing permission scope on the vendor's platform. Support can usually tell from the error code which side the problem is on.

Stuck or pending — not actually broken

• Job board postings sitting "In Progress" or "Not processed." VONQ (the engine behind LinkedIn, Indeed, and other paid job board postings) only validates your channel credentials at the moment a job is actually posted — not when you save the contract. There's no immediate feedback when you first enter credentials, so a contract can save successfully and only fail later, once a job tries to post through it. If a posting has been stuck for an unusually long time, that's worth flagging to support rather than assuming it will resolve on its own.

• Zero applicants shortly after a paid posting goes live. Job boards can take time to index and start driving traffic; a posting showing no applicants after a day or two isn't necessarily failed.

Known errors and limitations (real gaps, not something to work around)

• A generic flow error with no restart option. When a step in a flow (for example, a LinkedIn InMail step) fails with a generic error, Kula currently offers no way to retry or resume just that candidate — the only available action is Stop Flow, which removes the candidate from the flow entirely and can't be undone. This is a known product gap, not a setting you're missing.

• Duplicate-candidate merges can fail when both profiles have consent records. Because each contact can only hold one consent record, merging two profiles that each have their own consent status can trigger a database error rather than merging cleanly. This is an active engineering gap in the consent system, not user error.

• Unclear errors when adding, re-adding, or transferring a candidate into a job. A candidate transfer or add-to-job attempt that fails with a vague error (or a candidate showing as "already part of this job" when they don't appear on it) is almost always related to an existing or previous application record for that candidate on that job — including ones from an evergreen job or a transfer that happened earlier.

Specific error messages you might see

Kula surfaces some errors as plain integration-failure text — for example, an error naming a specific service and asking you to verify your API key, or an authentication error tied to a specific SSO provider — rather than a generic banner. If you see an error message quoting a specific integration or service by name, that's a strong signal the issue is with that connection rather than with Kula generally, and reconnecting or re-checking that integration's credentials is the first thing to try.

When Kula's own status display doesn't tell the whole story

Job board integrations are the clearest example: because credential validation only happens at posting time, Kula's own "In Progress" status can lag behind what's actually happened on the vendor's side by a meaningful amount of time. If something looks stuck and reconnecting doesn't help, don't assume the in-app status is the full picture — contacting support with the job or campaign link lets them check the vendor side directly.

Good to know

• Most things that look "broken" are disconnected integrations, not bugs — reauthenticating email, calendar, Zoom, or Slack resolves the majority of these in one click.

• If a flow step fails with a generic error, there's currently no way to restart just that step for that candidate — only Stop Flow, which permanently removes them from the flow. Read the confirmation before you click it.

• Paid job board postings (via VONQ) validate credentials only when a job actually posts, not when you save the contract — so a contract that saves without error can still fail later.

• An unclear error when adding, re-adding, or transferring a candidate into a job usually points to an existing application record for that candidate on that job, not a random glitch.

• When you contact support about an error, include the exact error text and, if it's visible, the request ID shown in the error — this is what engineering uses to trace exactly what happened on their end, and it speeds up diagnosis considerably.

FAQ

• I got an error from a job board integration saying my credentials are invalid, but Kula's status still shows "In Progress" — is that a miss on Kula's end? Not necessarily. Credential validation with most job boards only happens at the moment of posting, and there's no instant feedback loop when you first save a contract — so a delay between the vendor rejecting credentials and Kula's status reflecting that is expected, not a bug. If it's been outstanding for a while, contact support with the job link so they can check the vendor side directly.

• I reconnected my Slack integration, but it still shows as "Invalid" — why? If your Slack workspace isn't listed in the Slack app marketplace, Slack requires the reconnection to be completed by a Workspace Owner, not a Workspace Admin. Check who holds Owner in your Slack workspace and have them redo the reconnection.

• A candidate's flow step failed with an error, and now I can only stop the flow — is that permanent? Currently, yes — there's no restart option for a candidate stuck on a failed step, and Stop Flow removes them from that flow entirely. If you need the candidate active in outreach again, you'd need to add them to a new flow.

• Why does a candidate's self-schedule link say "No slots available" when my calendar clearly has open time? This almost always means your calendar integration has become disconnected, not that you're actually unavailable. Reconnect your calendar in Settings → My Integrations and the link should reflect your real availability again.

• What does it mean if a job board posting has been sitting "In Progress" for several days? It can mean normal processing delay, but it can also mean the job board rejected the credentials and that rejection hasn't yet been reflected in Kula's status. If it's been unusually long, reach out to support with the job link rather than continuing to wait.

Need help?

If you're seeing an error that isn't covered here, or a "known gap" above is actively blocking you, contact Kula support with the exact error text, the page or candidate/job URL where it appeared, and the request ID if one is shown — this is the fastest path to a resolution.