How to Resolve Runtime Error in Github Sync Project?

Help
1

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

Hello, I’m getting this runtime error in my Github Sync project. Could not resolve step[2].uses: filter-continue-workflow-condition@0.0.2
My project won’t deploy. Does anyone know how to resolve?

2

Hi Niel - could you clarify when this error is occurring? Is it happening during testing the workflow or during the deployment of the project?

Also, if you could share the Project with support (under the project settings) and share a link to it here, that would be very helpful so we can take a look into the logs.

3

The error occurs during deployment. The project is shared. I noticed that if you set a custom Github repo name and then update project settings, the repo name defaults to the actual project name in settings and creates a new repo.

4

Thanks - could you reshare the link to this specific project here?

5
6

Thanks Niel! Just what we needed. We’ll take a look.

Per the GH repo name change, I suspect this is an unhandled syncing event. Most changes should push from Pipedream → your specific Github Repo, but consolidating a remote repo name change might be problematic.

7

That error message is leading me to believe that the particular version of that action is no longer published in the Pipedream Component Registry. Could you try deleting the Filter > Continue Workflow on Condition action in your workflow and recreating it? That should update it to the latest published version.

8

I’ve tried to edit the workflow, but when I create a dev branch and click on the workflow to edit, it throws an error: “Workflow not found in development branch”

9

Should I try to edit the version number directly in the repo?

10

Yes that’s worth a shot, I would still make a new branch in your repo, modify that step and merge as a test

11

Where can I find the latest version number for the filter component?

12

The latest version should be visible on the action’s page in the component marketplace:

13

Or you can look at the Pipedream GH repository directly

14

https://github.com/PipedreamHQ/pipedream/blob/50242d93d30c2b84257d15d5aec2b6ea03ce[…]ons/continue-based-on-condition/continue-based-on-condition.mjs

15

Got it. I’ll try to edit the version number in the repo and see if that fixes it.

16

Didn’t work.

17

Actually, it did work. I didn’t pull the dev branch into production.

18

Thanks for your help!

19

Great :slightly_smiling_face: glad to hear it