Billing plan change page bug

[Marsredskies]

Preflight checklist

• [X] I could not find a solution in the existing issues, docs, nor discussions.
• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines.
• [ ] This issue affects my Ory Cloud project.
• [ ] I have joined the Ory Community Slack.
• [ ] I am signed up to the Ory Security Patch Newsletter.

Describe the bug

At console.ory.sh, when I change my plan from "Startup" to "Developer" in "Usage & Billing", this occurs: After refreshing the page, plan remains "Startup"

Reproducing the bug

1. Create a profile on console.ory,sh
2. Use "FIRST900" code for startup account
3. Try to change billing plan from "Startup" to "Developer"

Relevant log output

No response

Relevant configuration

No response

Version

cloud

On which operating system are you observing this issue?

No response

In which environment are you deploying?

No response

Additional Context

I'm aware of monthly bills, while I'm not using cloud version of kratos.

[aeneasr]

Thank you very much for the report! @zepatrik can you PTAL?

[zepatrik]

I tried a few times but could not reproduce it. I think this was only a temporary issue. Can you try again?

I get the expected result:

[Marsredskies]

Can we move to Slack #cloud channel? I try to change it like every 2 or 3 days and the same thing occurs. I’ve checked all elements and responses and found this error coming from server:

{"error":{"code":500,"status":"Internal Server Error","request":"f6cc64b5-47bb-9d0e-a914-e32d30efdb3a","message":"{\"status\":400,\"message\":\"You cannot update a subscription schedule that is currently in the released status. It must be in not_started, active status to be updated.\",\"request_id\":\"req_nVWE6sHtYiE5Mn\",\"type\":\"invalid_request_error\"}"}}

On 22 Jun 2022, at 14:05, Patrik @.***> wrote:

 I tried a few times but could not reproduce it. I think this was only a temporary issue. Can you try again? I get the expected result:

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

[zepatrik]

I see, with the response I now know that the issue is. We have it tracked already (https://github.com/ory-corp/cloud/issues/2410).

[aeneasr]

@zepatrik can we fix the subscription @Marsredskies is referencing to hotfix this issue?

[zepatrik]

No, the underlying issue needs to be fixed. We can cancel it if it is not possible for @Marsredskies, but can't fix it.

[Marsredskies]

It would be great, if you cancel this subscription, because I’m not using it and never did actually. Not even working in the project, where I planned to integrate it. Thanks in advance

On 22 Jun 2022, at 16:40, Patrik @.***> wrote:

 No, the underlying issue needs to be fixed. We can cancel it if it is not possible for @Marsredskies, but can't fix it.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[kmherrmann]

I've canceled your subscription now - sorry for the poor experience!

If I may ask - What stopped you from adopting Ory Cloud and what were you missing? Thanks a lot!

[Marsredskies]

Nothing really, I just quit that job and that integration left unimplemented, that’s it

On 22 Jun 2022, at 18:55, Klaus Herrmann @.***> wrote:

 I've canceled your subscription now - sorry for the poor experience!

If I may ask - What stopped you from adopting Ory Cloud and what were you missing? Thanks a lot!

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[Marsredskies]

And yeah, thank you for your support

On 22 Jun 2022, at 18:55, Klaus Herrmann @.***> wrote:

 I've canceled your subscription now - sorry for the poor experience!

If I may ask - What stopped you from adopting Ory Cloud and what were you missing? Thanks a lot!

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[kmherrmann]

Thanks! :)

[zepatrik]

This should be fixed now for new subscriptions, and should be fixed for all others probably today.