This topic was automatically generated from Slack. You can find the original thread here.
Hey I need help with a trigger working a bit weird.
I have a UI for configuring Pipedream Triggers, using the (now legacy) SDK and Documentation instructions.
I am trying to set up the linear-issue-created-instant trigger, for example.
Among some of its props, one of the only required ones is teamIds. This prop has both reloadProps and remoteOptions.
Since it has remoteOptions = true, at first I run configureComponent on this component to obtain the list of available options. In this case, it does return the correct items.
However, here’s the catch:
When I select one of these available elements, since it has reloadProps = true, I need to run fillConfiguredProps and configureComponent again.
Now, for some reason, when using the value in the configuredProps argument, not it returnsno available items. Not even the one I selected.
Based on your description, you’re running into an issue with the Linear “Issue Created (Instant)” trigger (linear-issue-created-instant) in the legacy Pipedream SDK, specifically with the teamIds prop that uses both remoteOptions and reloadProps. ### What you’re seeing - First load: configureComponent returns the correct list of teams for teamIds. - After selecting a team: When you run fillConfiguredProps and configureComponent again (with the selected value in configuredProps), the options for teamIds come back empty. ### Why this happens This is a known quirk with some legacy Pipedream components, especially those using both remoteOptions and reloadProps together. The root cause is usually one of the following: 1. The options method expects a different input shape: When you pass the selected value in configuredProps, the component’s options function might not be handling the input as expected, and so returns no results. 2. The options method is filtering out already-selected values: Some components are written to only show unselected options, so once you select a team, it disappears from the list. 3. Linear API edge case: If the underlying API call for teams is sensitive to the input or authentication context, it might return nothing if the wrong data is passed. ### How to debug/fix #### 1. Check the options method for teamIds If you have access to the component code, look for something like: teamIds: { type: "string[]", label: "Teams", async options({ auth, prevValue }) { // fetch teams from Linear API // return teams.map(team => ({ label: team.name, value: team.id })) } } - Does it filter out already-selected teams? - Does it expect a certain input shape for prevValue or configuredProps? #### 2. Try passing an empty array for teamIds in configuredProps Sometimes, if you pass the selected value as a string instead of an array, or vice versa, the options method breaks. Try ensuring teamIds is always an array, even if only one team is selected. #### 3. Compare with other triggers You mentioned other triggers work. Compare their options/remoteOptions methods to see if there’s a difference in how they handle the input. #### 4. Test with the latest UI If possible, try configuring the trigger directly in the Pipedream UI (not your custom UI) and see if the same issue occurs. If it works there, the issue may be with how your UI is passing configuredProps. — ### Workarounds - If you control the component code: Update the options function to always return all teams, regardless of input. - If you don’t control the code: As a workaround, you may need to manually enter the team ID, or ensure your UI always passes the correct shape for configuredProps. — ### Summary This is a common issue with legacy Pipedream components that use both remoteOptions and reloadProps. It’s likely due to how the options function is written or how your UI passes the selected value. Double-check the input shape and logic in the options method, and compare with working triggers for clues. — If you continue to have trouble or need a fix for a specific component, please contact Pipedream Support and provide details. They can help escalate or patch the component if needed.
Based on your description and the provided configuredProps: on { "linearApp": { "authProvisionId": "apn_XXXXXXX" }, "teamIds": ["some-uuid"] } Here’s how this relates to Pipedream Connect and component configuration: — ## How Pipedream Component Configuration Works When you call the component configuration API, you must pass: - external_user_id: your user’s ID - id: the component key (e.g., linear-issue-created-instant) - prop_name: the prop you want to configure (e.g., teamIds) - configured_props: an object of already-configured props The configured_props object should use the prop names as defined in the component code. For example, if the prop is called linear in the component, you must use "linear": { ... } in configured_props, not "linearApp". — ## Potential Issue If the component’s prop is named linear, but you use linearApp in configuredProps, the component may not recognize the authentication and fail to fetch options. This is a common source of issues when configuring components. — ## What You Should Do 1. Check the Component’s Prop Names: - If the component defines: props: { linear: { type: "app", app: "linear" }, teamIds: { ... } } Then your configuredProps should be: on { "linear": { "authProvisionId": "apn_XXXXXXX" }, "teamIds": ["some-uuid"] } 2. Use the Correct Key: - Replace "linearApp" with "linear" (or whatever the prop is named in the component). 3. Configure Props in Order: - When configuring teamIds, make sure the linear auth is already set in configuredProps. — ## Example: Correct Usage on { "linear": { "authProvisionId": "apn_XXXXXXX" }, "teamIds": ["some-uuid"] } — ## Summary - Double-check the prop names in the component code. - Use those exact names as keys in configuredProps. - If you use the wrong key (like linearApp instead of linear), the component won’t be able to fetch options or function correctly. — If you’ve confirmed the prop names are correct and still see issues, this could be a component-specific bug or a legacy quirk. In that case, please reach out to Support - Pipedream for further help.