Skip to content

[Docs] troubleshooting step uses error #14684

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 19, 2024
Merged

[Docs] troubleshooting step uses error #14684

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
cdf816a
add step uses error resolution
andrewjschuang Nov 19, 2024
d8482b8
add github sync troubleshooting redirect
andrewjschuang Nov 19, 2024
88b8e1a
edits
andrewjschuang Nov 19, 2024
eebc66f
fix deleted part
andrewjschuang Nov 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs-v2/pages/projects/git.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,6 +198,18 @@ Yes, you can use the GitHub Syncing feature to develop your workflows from YAML

Then pushing changes to the `production` branch will trigger a deploy for your Pipedream workflows.

### How can I fix the error about "could not resolve step[index].uses: component-key@version":
When you publish a private component to your workspace and reference it in a workflow, the workspace name should be prefixed in the component key in your `workflow.yaml` configuration file.

For example, if you modified a [registry action](https://pipedream.com/docs/apps/contributing) and published it to your workspace, the correct component key is `@workspacename/component-key@version` (e.g. `@pipedream/[email protected]`).

1. Clone your repository locally and create a dev branch.
2. Find the line of the error and add the workspace name prefix to the component key.
3. Commmit your change and push it.
4. Open your project in the Pipedream UI, select your dev branch.
5. Click on Merge to Production and verify if the workflow deployment was successful in the [Changelog](https://pipedream.com/docs/projects/git#use-the-changelog).
6. If you need further help, [reach out to support](https://pipedream.com/support).

### Why am I seeing an error about "private auth mismatch" when trying to merge a branch to production?
![Private Auth Mismatch](https://res.cloudinary.com/pipedreamin/image/upload/v1704258143/private_auth_mismatch_kzdd7e.png)

Expand Down
4 changes: 4 additions & 0 deletions docs-v2/pages/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,10 @@ If you're encountering a specific issue in a workflow, try the following steps,

If you're still seeing the issue after trying these steps, please reach out in [the community](https://pipedream.com/support).

## I need help with my GitHub Synced Project

[See FAQ here](https://pipedream.com/docs/projects/git#frequently-asked-questions).

## Why is my trigger not emitting events?

Most Pipedream sources fall into one of two categories: webhook-based or timer-based.
Expand Down
Loading