Linear API Errors

Git-Zen talks to Linear through Linear’s GraphQL API. When a Linear call fails, the sidebar usually shows a general message, such as There was an issue with your request. It does not show the Linear error text. This page lists the common causes and how to fix them.

An issue is not created

Check these causes:

• The estimate does not fit the team’s scale. Git-Zen offers 1, 2, 3, 5, 8, 13, and 21 for every team. If your team uses another scale, choose None. See Additional fields.
• The team is archived, or the OAuth user lost access to it. Click the Webhooks icon, then Clear Repository Cache, and try again.
• The token is no longer valid. Re-authorize.

A label is missing from the new issue

Git-Zen does not create Linear labels. If a label name does not match an existing label in the team or the workspace, Git-Zen leaves it off. It does not show an error. Create the label in Linear, or choose an existing label.

The issue appears in the sidebar but Zendesk gets no updates

• Make sure the issue description still has the reference tag, for example gz#12345.
• Make sure the issue is in a public team. Linear does not send events from private teams to the Git-Zen webhook.
• Make sure the Git-Zen webhook still exists in Linear. See Check the webhook in Linear.
• Make sure the ticket is not closed. See Updates to closed tickets.
• Check for a Solved ticket with required fields. See Troubleshooting.

The Linear API is down

You can check Linear’s status at status.linear.app. During an outage, sidebar actions fail, and Linear may not deliver webhook events. Git-Zen does not replay missed events. After Linear recovers, make a small change to an affected issue in Linear to send a new event.

When to contact support

If these steps do not help, contact support. Include:

• The exact message that the sidebar shows
• The Linear issue identifier, for example ENG-42
• The Zendesk ticket ID
• The approximate time of the error