Skip to main content
If something is not working as expected with the Linear integration, the sections below cover the most common problems and how to resolve them. Each issue includes the most likely causes and clear steps to get back on track.
If NOCK shows a connection error immediately after you paste and save your Linear API key, one of the following is usually the cause.Check that the key is valid and completeLinear API keys are long strings that begin with lin_api_. Make sure you copied the entire key from Linear — a truncated key will always fail. If you are unsure, return to Linear → Settings → API, revoke the existing key, and create a new one.Check that the key has not expired or been revokedLinear personal API keys do not expire automatically, but they can be manually revoked. In Linear → Settings → API, confirm that the key you created is still listed and has not been revoked.Check that the account has the right access levelNOCK needs the key’s associated Linear account to have at least Member access to the workspace. If you generated the key from a guest account, it may not have sufficient permissions. Try generating a key from an account with Member or Admin access.
After fixing the issue, return to Settings → Integrations → Linear in NOCK, clear the existing key, paste the new one, and click Save again.
If tickets appear in NOCK but no corresponding issues show up in Linear, work through these checks in order.Confirm team and project are selectedGo to Settings → Integrations → Linear and check that a team is selected in the Team dropdown. If no team is selected, NOCK does not know where to route new issues.Check that your project still existsIf you selected a specific project and that project has since been archived or deleted in Linear, issue creation will fail silently. Either select a different project or set the Project field to None.Verify the API key is still validAPI keys can be revoked at any time from Linear. If the key was rotated or revoked after you first connected, NOCK loses the ability to create issues. Go to Settings → Integrations → Linear and re-enter a fresh API key.
Changes to team and project settings take effect for new tickets only. Tickets that were submitted while the settings were misconfigured will not automatically be sent to Linear. You will need to forward those tickets manually if needed.
Status sync is normally near real-time, but there are a few reasons it can fall behind or stop.Wait a moment and refreshBrief delays of up to a minute can occur during periods of high activity. Refresh the ticket in NOCK and check whether the status has caught up before investigating further.Check that your integration connection is intactNOCK receives status-change notifications from Linear automatically as part of the integration. If this connection was disrupted, sync will stop. Contact NOCK support if you suspect the integration link needs to be restored — do not attempt to reconfigure it manually, as this may cause duplicate events.Confirm the API key is still validIf the API key was revoked or rotated after the initial setup, NOCK can no longer receive or process sync events. Re-enter a valid API key in Settings → Integrations → Linear.
If status sync has been interrupted for an extended period, NOCK tickets may show stale statuses. After restoring the connection, statuses will update on the next activity for each issue but will not retroactively re-sync all historical changes automatically.
If new issues are appearing in a different team than you intended, your routing setting needs to be updated.Update the team selectionGo to Settings → Integrations → Linear and select the correct team from the Team dropdown, then click Save. All issues created after saving will go to the new team.
Updating the team does not move issues that were already created in Linear. Those issues remain in the original team. You will need to move them manually in Linear if required.
Check for multiple NOCK projectsIf your NOCK account has more than one project, each project has its own integration settings. Make sure you are editing the settings for the correct NOCK project.
If the import finishes instantly with zero results, or brings in far fewer issues than you expected, these are the most common causes.Check API key permissionsThe API key must belong to a Linear account with at least Member access to the selected team. A key from a guest or restricted account may not have read access to issues in that team.Confirm you have the right team selectedThe import pulls from the team currently selected in Settings → Integrations → Linear. If you have multiple teams in Linear, make sure the correct one is selected before running the import.Check that the team has issuesIf the selected team is brand new or has no issues in its backlog, the import will return nothing — which is expected. Switch to a team that has existing issues if you want to import historical data.Check for archived issuesNOCK’s import fetches active issues. Cancelled or archived issues in Linear may not be included in the import results. This is expected behaviour.
If you still see fewer issues than expected after checking the above, try disconnecting and reconnecting the integration with a freshly generated API key, then run the import again.

​
Still need help?

If the steps above do not resolve your issue, reach out to NOCK support with the following information to speed up diagnosis:
  • The error message you are seeing (a screenshot is helpful)
  • The Linear team and project you have selected in NOCK
  • Whether the issue affects all new tickets or only specific ones
  • Approximately when the problem started