Unable to connect: "Failed to save sync" about synclinear.com

[tedspare]

Thanks for sharing the payload, @vanessayuenn. I've manually added the Linear team to the DB. The team's webhook should show as "deployed" now in the UI. Wanna try syncing one last time (leaving your webhooks + tokens as they are now)?

I'll look into what's causing that save to fail.

[tedspare]

Thanks for raising this @vanessayuenn! Your explanation seems very plausible. Orphaned data would break some of the setup steps.

If you'd like that data to be wiped for a fresh start, which repos and Linear teams should I remove? If that doesn't work, I'll try to replicate this.

[vanessayuenn]

@tedspare this would be for: storybookjs/storybook on GitHub and Storybook on Linear. Thank you!

[tedspare]

Removed, thanks! Please let me know if it fails to save again.

[vanessayuenn]

@tedspare thanks, but unfortunately I am still getting the same "Failed to save sync" error.

However, I think when you removed things on your DB end, I still had the webhooks installed on both GitHub and Linear; not sure if that would have caused any issue. I have now removed the webhooks from both sides. Perhaps you can try again?

[tedspare]

All good - I've removed them again. Does that work?

[vanessayuenn]

@tedspare sorry this issue still persists. I should also share that the GitHub webhooks keep failing with the error "Could not find issue's corresponding team":

[tedspare]

Interesting - thanks @vanessayuenn. This error means the repo/team (or actual issue) wasn't found.

Did the "Failed to save sync" error persist, or were you able to set the app up?

[vanessayuenn]

@tedspare no i still get the "failed to save sync" error on synclinear.com side, and the "Could not find issue's corresponding team" error is on GitHub's webhook side (on all types of delivery). I also cross-check the request bodies on calls to synclinear.com/api/save vs GitHub webhook deliveries, the repoId and userId match between the two calls.

[tedspare]

Thanks for the details - I haven't found the source of the error yet, but here are two more options:

• If you log into the dashboard at SyncLinear.com, do you see any active syncs (see pic)? If so, could you try removing then re-syncing them?
• Otherwise, we could try resetting once more. If so, just let me know when you've deleted both webhooks manually and I'll reset your records in the DB.

[vanessayuenn]

Nope, I had not been able to get pass the deploy webhooks step to get to the screen you shared.

Ok let's try this again. Here is everything I have removed:

• Authorized application installed on Linear
• Authorized OAuth App installed on my profile on GitHub
• webhook on GitHub repo
• webhook on Linear

Is there something else I missed? Perhaps we can go one step further, not just resetting records for team on Linear and repo on GitHub, but my records as a user from the DB as well. Thanks again for all the help so far!

[tedspare]

Thank you for bearing with me @vanessayuenn! This is the trickiest bug so far in this project.

Here's what I've removed:

• storybookjs/storybook GitHub repo record

Finally noticed I haven't seen the Storybook Linear team in the DB, and its absence seems to be breaking the save. Is it possible that team has another name (eg. Engineering, Sandbox, Design, etc), a custom ID in Linear, or some special permission preventing its ID from being returned?

Otherwise, feel free to try again and if it fails again, I can add the team manually. Storybook is probably a huge org too - happy to help set up self-hosting.

[vanessayuenn]

@tedspare I appreciate you working with me on this weird bug! It looks like the linear team ID did get returned, but for some reason cannot be written into the synclinear database; the error returned did not have details. Pasting the payload and response on /api/linear/save call:

payload object: {
    "teamId": "cf44ea4c-b6e2-4f26-97f0-09fc66a8d2f5",
    "teamName": "Storybook",
    "publicLabelId": "f30a265a-1d99-4387-9696-32a0ef9c40df",
    "canceledStateId": "e0807107-25d4-49e7-9378-fc1b0c775049",
    "doneStateId": "fafbf2f2-7370-4848-abbe-9f894cf98626"
}
error response: {
    "error":{"clientVersion":"3.15.2"}
}

Our team is actually pretty small, but if it's still a dead end from here, I will look into the self-hosting option also.

[Sandhukhizar61]

Camera file is not opening.

[tedspare]

Hi @Sandhukhizar61 - not sure I understand what you mean but feel free to open a new issue!