Why Does the Linear Project Update Created (OAuth) Trigger Stop Working Showing Error 'Cannot Read Properties of Undefined'?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

I’ve been using the Linear Project Update Created (OAuth) trigger. It seems to work for a while, then stop working. When I check the source logs, I see errors like this:

TypeError: Cannot read properties of undefined (reading 'teamsInfo')
at Object.isRelevant (file:///pipedream/dist/code/81bd99610a7b6dc96bb16342185509ad65dfd37b2fa446b1cede598d3d594354/node_modules/.pnpm/@pipedream+linear_app@0.7.1/node_modules/@pipedream/linear_app/sources/new-projectupdate-created/new-projectupdate-created.mjs:64:46)
at Object.run (file:///pipedream/dist/code/81bd99610a7b6dc96bb16342185509ad65dfd37b2fa446b1cede598d3d594354/node_modules/.pnpm/@pipedream+linear_app@0.7.1/node_modules/@pipedream/linear_app/sources/common/webhook.mjs:206:54)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:105:11
at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)
at async deployedComponentMain (/var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:44:20)
at async MessagePort.<anonymous> (file:///var/task/component_maker.mjs:198:9)

Is there a misconfiguration on our end or is this a bug?

2

Hey , could you share the source ID?

3

Hey , thanks, it’s dc_yLu117R.

4

Thanks , it seems the Linear webhook payload has changed and we need to update (fix) our trigger.

Could you do us a favor and report this issue in our public repo? Please add the webhook body (remove sensitive information) you see in your source logs.

  1. Head over to Support - Pipedream
  2. Click on the “Request an Integration” card.
  3. Select “B - Request changes to an existing integration.”
  4. Fill out the form with details of the issue.
    This way, it gets logged in our public repo, and the component development team can be notified!
5

Link the created issue here and I can prioritize it!

6

Thank you, ! Logged #17445

7

Thanks, I prioritized it