LNTWOOL - the pains with buildship continue. So...
the pains with buildship continue. So i accidently deleted a pretty critical workflow. That's on me, I was on the plan with support but downgraded after the constant issue, so i don't believe i get formal support, but i sent in a ticket to buildship letting them know i deleted a critical workflow is there anything they can do.. I don't think i have ever sent a ticket where i actually got a response. Anyways i rebuilt everything. Here's the problem, and frustrating. Buildship is keeping it around somewhere, becuase the API POST URL, is still "taken", as in my instance is still somewhere.. if i can't get suppor tto respond what do i do here, i need that path to be available
6 Replies
Hi @LNTWOOL could you please DM your email or share workspace ID?from which you sent support request? We can check.
DMing now
well ill just do it, here, is this what you need. project id: buildship-0nfjbb, bucket_id: buildship-0nfjbb-us-west1
thanks for sharing. I checked, and you are on a starter plan, do you happen to have the web URL of that workflow? without the workflow ID, it can't be restored.
How do i get that if its deleted?
And at this point im not even asking for it to be restored (that would be nice), but the expected behavior if it's deleted, then i should be able to use the deleted flow's API trigger endpoint, but build ship will not let me, it says it another flow has it. I have run into this twice before, i delete an entire flow, i try to use the API trigger end point that was deleted, and i can't
Endpoint meaning /linked/kai in my environment. That was deleted obviously when i deleted the entire flow, yet buildship says it's still there, it's been a week
hello any update??? i simply need to reclaim the api endpint /linked/kai.. this is a bug, it has been deleted, it should not still be there @Harini
it's a separate issue from the one you sent initially. (restore workflow)
@LNTWOOL could you please now try to connect and ship/deploy
/linked/kai endpoint, it should work. We are now tracking this issue.ah thank you, yes i can now use the end point. thanks