#copy volume didn't work?
24 messages · Page 1 of 1 (latest)
Project ID: 004e54e7-64a6-467d-960d-379e6d29e925,2665b49c-4fab-405a-a4c2-4983422dad1f
looks like it was canceled while it was in the queued state, you didnt cancel it?
no
but I opened the PR environment before it deployed the changes
anyway i'll just open a new PR
so yeah it happened again
env id: aff764f6-47f3-46bb-bef1-5267252ea99d
what happens if you disable copy volume data?
it probably works but i need copy volume data
volume voluma data is beta
thats why im reporting it
for sure, just saying it would be unwise to put yourself into a position where you need a beta feature
follow up, I believe I know what the issue is, and if so, we have a fix in the works, funny enough if it's what I think this issue is, it doesn't have to do with copy volume data, although I could eat my words, we will have to wait and see
fix has been in place, let me know if you see the missing deployment issue again
will try it out
got a failed to create deployment
https://railway.com/project/004e54e7-64a6-467d-960d-379e6d29e925/service/1bff3ff4-6b65-4182-96cf-b7b676b48a1c?environmentId=c78a6765-b507-48e8-946c-9bb4d1931daf
for Notus API?
timescaledb
oops i closed the PR 
i'll enable the copy volume again and create another PR
okay now this is a completely different error than it was the first time, so the initial issue was solved.
i'll add this thread to our ticket for the current error, in the mean time you would need to disable the beta feature unfortunately.
hey @frank crypt - we believe to have identified the issue and implemented a fix for it, please re-enable and let me know if you see the issue again