Running Linear?

Linear API or cycles behaving oddly? We unstick it.

Linear is the sharpest project tool in the current field, right up to the week a cycle rolls over the wrong issues, the GitHub sync leaves branches orphaned, or a Zapier automation spams half a workspace. We pick up the API rate limits, the broken cycle rules and the migration you started and did not finish, and get the workspace back to the quiet state you first adopted it for.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

linear-api.log

still broken

What it is

Linear at a glance

Linear is a project management tool for software teams, founded in 2019 by former Coinbase and Uber engineers. It has become the default choice for modern SaaS teams that found Jira too heavy and Trello too thin, and it now runs the backlog for a large share of US startups.

The product is built around issues, cycles, projects and roadmaps, with first-class GitHub and GitLab integrations, a GraphQL API and a growing set of agent-style automations. The design opinions are strong, which is part of its appeal; it is also why teams occasionally find themselves wedged against a behavior that is deliberate and not configurable.

Type
Project and issue tracking for software teams
First released
2019
License
Proprietary SaaS, per-seat pricing
Maintained by
Linear Orbit, Inc.
Typically used for
Issue tracking, cycles, projects, roadmaps, GitHub and GitLab integration, product engineering workflows

The honest version

Linear pros and cons

No technology is all upside. This is where Linear earns its place and where it tends to cause trouble.

Where Linear is strong

  • Fast, quiet, keyboard-firstThe app is responsive, the shortcuts are consistent, and engineers actually open it. That is the hardest trait to find in a project tool.
  • Cycles turn into a cadenceShort cycles with carry-over rules give a team a weekly rhythm without needing a scrum ceremony on top.
  • GitHub and GitLab integration is first-classBranches, pull requests and issue status flow in both directions, so an issue closes when a PR merges rather than when someone remembers.
  • Clean GraphQL APIScriptable, well documented, and more approachable than Jira's REST-and-webhook sprawl.
  • Opinionated defaultsThe product resists the Jira-style sprawl of custom fields and parallel workflows, which keeps workspaces usable years in.
  • Insights without a BI projectVelocity, cycle-time and completion views are built in, which answers the common engineering-manager questions without a separate dashboard.

Where Linear bites

  • The opinions can be a wallWorkflows that do not fit Linear's model (complex approvals, cross-functional dependencies) need workarounds or extra tools.
  • GitHub sync drifts under loadBranch and PR events can arrive out of order, leaving issues in states that look wrong until someone nudges them.
  • API rate limits bite integrationsA chatty Zapier flow, a sync job or a bulk import can hit the limit and stall for an hour, with little guidance on what to turn down.
  • Automations amplify mistakesA misconfigured Zapier or native automation can fire hundreds of times before anyone notices, polluting the workspace.
  • Cycle rollover rules confuse teamsWhich issues go to the next cycle, which drop to backlog, and which stay in the current cycle depends on settings most teams never consciously configured.
  • Not a great fit for non-engineering teamsMarketing, legal and ops teams often find the tool too engineering-shaped and end up back in a spreadsheet.

Sound familiar?

Common Linear problems we fix

The Linear problems that bring people to us, and what you have once each one is fixed.

rate limited, retry after 60s

Integrations hit the API rate limit

A sync job polls aggressively, a Zap fires on every issue update, or a backfill pulls the entire history. The API throttles and real users start seeing stale state in the UI.

Traffic shaped, integrations throttled

Cycle rolled over with 11 unresolved

Cycle rollover moved the wrong issues

The default rollover policy pushed in-progress work to the next cycle and backlog items into limbo, and the team spent the first day of the new cycle sorting the mess.

Cycle policy explicit and reviewed

GitHub webhook secret mismatch

GitHub integration stopped syncing

A secret was rotated, a repo was transferred, or the integration was reinstalled, and events are no longer being accepted. Issues and PRs drift apart.

GitHub sync restored, drift cleared

Zap fired 847 times

An automation is spamming the workspace

A Zapier zap, a native automation, or an AI integration triggered a loop on an issue update, flooding notifications and polluting activity feeds.

Automation bounded with guards

channel_not_found #eng-notify

Slack notifications stopped arriving

A channel was renamed or archived, the Linear integration never got updated, and notifications about in-progress work stop going anywhere.

Notification routing current

Triage inbox: 143 open

Triage inbox is a graveyard

No owner for triage, items pile up, and bug reports from customers rot for weeks before anyone looks.

Triage owned with a cadence

field 'parent' on CycleCreateInput removed

API breaking change caught us

A Linear API field was deprecated and removed, an internal tool was built against it, and the next release of the tool fails on a field that no longer exists.

Tooling updated to current schema

What we do

Linear help, from workspace rescue to automations

Pull us in for one broken integration, or let us run the whole workspace overhaul.

Rescue
GitHub sync drifting, automations running wild, or a cycle rollover that scrambled a sprint. We stop the bleeding and restore a calm state that the team can navigate.
Workspace design
Teams, projects, labels, priorities and workflow states shaped to how your org actually works, with the parts of Linear that are configurable and the parts that are not.
API and integration work
Scripts, syncs and Zapier flows built with rate limits in mind, schema watched for breaking changes, and alerts when a webhook starts failing.
Cycle and roadmap operation
Cycle cadence and rollover rules tuned, roadmap statuses tied to real work, and insights views that answer the engineering-manager questions without a separate dashboard.
Migrations
Jira, Trello, GitHub Issues or Asana onto Linear with field, status and history mapped carefully rather than dumped in bulk.
Managed Tech
A standing engagement that monitors integration health, keeps automations sane, and gives you an engineer on tap the week something goes sideways inside the workspace.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Linear alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Linear questions

Something else? Call+1 737 727 7327

Why does our Linear API integration keep getting rate-limited?

Usually a chatty automation that polls on an interval rather than listening to webhooks, or a backfill script that pulls the full issue history in one go. We switch the integration to a webhook-first model, batch the remaining polling, and respect the retry-after header the way the client library suggests.

How do we stop cycle rollover from moving the wrong issues?

Set the rollover policy explicitly in each team's settings rather than relying on the default, decide what happens to in-progress, blocked and unstarted work, and run a dry-rollover with the team before the cycle actually flips. The settings are per-team, which trips up workspaces that look consistent on the surface.

Our GitHub integration keeps falling out of sync. What do we do?

Confirm the webhook is still delivering, reinstall the integration if a repo was transferred, and check that the Linear app has access to every repo in the org rather than only a historical subset. We then run a reconciliation pass that pairs issues to PRs by reference until drift is zero.

Can we move from Jira to Linear without losing history?

Yes, with care. Statuses, custom fields and parent-child relationships need to be mapped deliberately, not dumped. We script the import, bring attachments across, keep issue IDs referenced in commits and PRs, and run the two systems in parallel long enough to be sure nothing was lost.

How do we get non-engineering teams to use Linear?

Often you do not. Linear is a software-engineering tool first, and marketing or legal tend to be happier in a tool that was built for them. For teams close to engineering, like design or product, we tailor the workspace so the engineering-shaped assumptions are mostly out of the way.

How much does Linear help cost?

The estimate is free of charge. Describe the integration error, the cycle you want tuned or the migration scope, and we send a fixed price before touching the workspace.

Free estimate

Linear giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.