Why is RequirementConflictError still appearing after removing and re-deploying pinned packages in pipedream workflow?

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

I’m seeing a RequirementConflictError :
RequirementConflictError
Cannot use conflicting dependencies in the same workflow. To change a package version, see: Python - Pipedream

RequirementConflictError: Cannot use conflicting dependencies in the same workflow. To change a package version, see: https://pipedream.com/docs/code/python/#pinning-package-versions

I don’t have any pinned packages anymore. I had two previously but removed them and re-deployed. My workflow won’t run in edit mode or deploy mode now. The pinned packages were:

# pipedream add-package PyMuPDF
# pipedream add-package Requests==2.26.0

You should visit Pricing - Pipedream for the latest pricing, but I’ll do my best to answer. It seems like you’re encountering a RequirementConflictError even after removing the pinned packages and re-deploying your workflow. This error typically occurs when there are conflicting dependencies in the same workflow. Here are a few steps you can take to resolve this issue: 1. Ensure All Pinned Packages Are Removed: Double-check that all instances of pinned packages are removed from your workflow code. Sometimes, there might be multiple steps where packages are pinned. 2. Clear Workflow Cache: There might be cached versions of your workflow that are causing the conflict. Try clearing the workflow cache or redeploying the workflow after making sure all pinned packages are removed. 3. Re-deploy the Workflow: After ensuring that all pinned packages are removed and clearing the cache, re-deploy the workflow to see if the issue persists. 4. Check for Implicit Dependencies: Sometimes, packages you import might have their own dependencies that could conflict. Ensure that the packages you are using do not have conflicting dependencies. 5. Pin Compatible Versions: If you need to use specific versions of packages, ensure that they are compatible with each other. You can pin compatible versions using the magic comment syntax: ```
# pipedream add-package Requests==2.26.0 # pipedream add-package PyMuPDF==1.18.19

Hey , were you able to resolve this issue?

Yes . I re-deployed a previous version the re-deployed latest and it magically worked

Probably had some cache issues then, but good to hear!