This topic was automatically generated from Slack. You can find the original thread here.
I’ve made a bunch of changes to a current deployment that have broken it beyond repair. I’m trying to go back toedit the current deployment (from May). I dont really want to have to deploy the broken code in order to go backto the May deployment. How do I do that?
It sounds like you’re trying to revert your workflow to a previous state without deploying the broken changes. Unfortunately, Pipedream v2 does not support automatic version rollbacks to a prior version of a deployed workflow. However, you can still edit a deployed workflow. Here’s what you can do: 1. Manually Revert Changes: If you have a record of the changes you made, you can manually revert the workflow to its previous state by editing the workflow in the Pipedream UI. 2. GitHub Sync: If you have your workflow synced with GitHub, you can revert to a previous commit. This way, you can restore the workflow to a state before the changes were made. For more information on enabling GitHub sync, visit this link. 3. Create a New Workflow: As a last resort, you can create a new workflow and manually copy the code and steps from the previous deployment (from May) to the new workflow. For more detailed guidance, you can visit the Pipedream documentation. If you need further assistance, please visit Support - Pipedream. I hope this helps! Let me know if you have any other questions.
And is there a risk to deploying the broken code for 5minutes and then reverting to the May deployment?
To better assist you with your question, I need a bit more context. Specifically: 1. What kind of deployment are you referring to? Is it a Pipedream workflow or another type of deployment? 2. What do you mean by “broken code”? Are there specific errors or issues you are encountering? 3. What is the significance of the “May deployment”? Is it a previous version of your code that was working correctly? Understanding these details will help me provide a more accurate and helpful response.
I’ve made a bunch of changes to a current deployment that have broken it beyond repair. I’m trying to go back toedit the current deployment (from May). I dont really want to have to deploy the broken code in order to go backto the May deployment. How do I do that?
It sounds like you’re trying to revert to a previous version of your workflow without deploying the broken changes. Unfortunately, Pipedream v2 does not support automatic version rollbacks for deployed workflows. However, you can still edit your deployed workflow. Here are the steps you can take: 1. Edit the Deployed Workflow: You can manually revert the changes by editing the deployed workflow to match the state it was in during May. This might involve copying and pasting code or configurations from backups or previous versions you might have saved. 2. Use GitHub Sync: If you have GitHub sync enabled, you can revert to a previous commit that represents the state of your workflow in May. This will allow you to see the full commit history and revert to a specific commit. For more details, you can refer to the Pipedream documentation on migrating from v1: > ### Rolling back a specific version > In v2, you can test and save your progress on a workflow without deploying it. > However, after deploying it’s not possible to rollback to a prior version of a deployed workflow. > You can still edit a deployed workflow, just like in v1 but automatic version rollbacks are not currently possible. If you need further assistance or have any other questions, please visit Pipedream Support. I hope this helps! If you have any other questions or need further clarification, please let me know.
it’s not possible to rollback to a prior version of a deployed workflow??
since when?
You are correct. In Pipedream v2, it is not possible to rollback to a prior version of a deployed workflow. This change allows you to test and save your progress on a workflow without deploying it, but once deployed, automatic version rollbacks are not currently possible. For more details, you can refer to the migration guide. If you have any further questions or need more assistance, please let me know!
I think we might not have documented or announced this yet, but have you seen the Revision History beta feature?
I have yes, I’m just not able to use it correctly for whatever reason. I keep clicking restore, but then when i try to edit it shows me the broken workflow again.
Hm that’s strange. If you’re able to maybe take a screen recording of what’s happening there, happy to take a look.
(ie test it)
After you click Restore this version, then you should be able to click in to any step to edit it, let me see if that’s working for me
Yea that’s working as expected for me. What happens when you click Restore?
when I click restore It displays the old workflow (without the erroneous steps I created). I can copy any of the previously functioning code,but I can’t edit that code, or run the test on it
Can you show me a screenshot of that state where you can’t edit the code or test a step?
I see the Restore version is still blue and “primary”, which it shouldn’t be after you’ve clicked it
