tom - Seems my migration to v2 failed. I'm rath...
Seems my migration to v2 failed. I'm rather sure I clicked all the right buttons but still can only use v1 ðŸ˜
15 Replies
Hi @tom could you please share this via in-app support from current version, we’ll check and fix for you
Hi, @Gaurav Chadha wrote to support. I somehow got the migration done, but now I'm getting a "no credits" error, even on v1 flows. How is this possible?
HI Tom, yeah we are fixing for your project. Will be updated shortly
Any news? This is definitely not what I was expecting from the v2. Seems like the credit conversion would be a key feature of the migration.
We have fixed your project and updated the credits you can access your project at - app.buildship.com. @tom sent you an email
Thank you @Gaurav Chadha for the quick response. I'm still seeing the "you're poor" indication on UI but the API seems to work 🙂
@Gaurav Chadha I am getting failed to shipping workflow! I opened in-app support!
@Gaurav Chadha the credits are now back, but I can't seem to delete workflows anymore. Clicking on the force delete does nothing..
@tom could you share a jam.dev recording via in-app support mentioning the issue, we'll check the issue and fix.
@Gaurav Chadha I don't think this reproducing this is complex, just select delete - get error - click force delete - observe that nothing happens. (Thank you for the incredibly quick response)
it works for other users, requesting via in-app support with jam.dev to checkout if it's an issue with your workspace this way we'll be able to track and resolve the issue faster with the team.
Created a ticket, but forcing me to use some new app to just record a error message which tells me "failure" doesn't make a lot of sense. The fact that it works for other users and not for me, is the basis why I'm reporting it, you have to help me out here by explaining how could that justify over complicating bug reporting?
I've tested deleting the "test" workflow on your app, and it was deleted successfully. We request jam. dev recording to catch the specific bugs. It's a process of debugging. Also, note: deleting the folder (containing) doesn't work we'll update this UX.
Thanks for testing it. While I appreciate the quick response from you, I think it would work better acknowledging there might be an issue and solving it might take some time. Steps to reproduce: delete - see error - click force delete - nothing happens. ðŸ˜
ok, got the issue, we'll be pushing the fix and will let you know here as well on email