Are there any known bugs with the Linear OAuth trigger endpoints causing deployment failure with Pipedream due to an "observation error"?

Bugs
1

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

hey guys, are there any known bugs with the Linear oauth trigger endpoints?

i’m getting the following issue when trying to deploy a trigger with the following options:

🔄 Deploying trigger to Pipedream with ops: {
  "id": "linear-new-issue-status-updated",
  "configuredProps": {
    "teamId": "7f8c6250-c3d7-430d-a7c1-5054a6c0e24c",
    "linearApp": {
      "authProvisionId": "id"
    }
  },
  "external_user_id": "userId",
  "webhook_url": "webhookUrl"
}
Failed to deploy trigger to Pipedream: Error: Status code: 422
Body: {
  "error": "observation error",
  "err": null,
  "observations": [
    {
      "k": "hook",
      "ts": 1756480084436,
      "h": "activate"
    },
    {
      "k": "error",
      "ts": 1756480084629,
      "err": {
        "name": "TypeError",
        "message": "Cannot read properties of undefined (reading 'endpoint')",
        "stack": "TypeError: Cannot read properties of undefined (reading 'endpoint')\n    at Object.activate (file:///tmp/__pdg__/dist/code/7178e2063603f841c9d6364b318bb5f4a4934cbb7a00cade01068152f824b535/node_modules/.pnpm/@pipedream+linear_app@0.7.5/node_modules/@pipedream/linear_app/sources/common/webhook.mjs:141:26)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async /var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:78:13\n    at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)\n    at async deployedComponentMain (/var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:44:20)\n    at async file:///var/task/component_maker.mjs:203:11"
      }
    }
  ]
}
    at P.anonymous (.next/server/chunks/9699.js:1:48467)
    at Generator.next (anonymous)
    at g (.next/server/chunks/9699.js:1:41294) {
  statusCode: 422,
  body: [Object],
  rawResponse: [Object]
}
2

I’m getting the same error with the api key version

3

Stripe or Linear?

4

Whoops Linear, my bad there

5

good catch

6

Let me check the demo app

7

Hm it does seem to be working on the demo app. Must be something on my end, I’ll take a look. Thank you!

8

Did you run the reloadComponentProps?

9

That’s my guess

10

I did, I think the issue is I didn’t pass the dynamicPropsId

11

Ah makes sense

12

I’ll start checking the demo app before coming here, thanks Andrew :raised_hands:

13

That’s a good place to check! Np glad to help!