Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Button inputs made by the users aren't working. #1743

Open
meatboymeatboy opened this issue Aug 26, 2024 · 3 comments
Open

Button inputs made by the users aren't working. #1743

meatboymeatboy opened this issue Aug 26, 2024 · 3 comments

Comments

@meatboymeatboy
Copy link

Whenever one of the flows has a button, when testing through the viewer, the buttons do not work. When clicking on any of the options to follow the flow, it freezes, and the same button options keep appearing, as if the user hadn't chosen anything yet. If theres no buttons, it flows normally.

If I test the flow through the builder view, it works normally, but the published flow looks like this.

Steps to reproduce the behavior:

  1. Go to https://maga.magadoslots.online/install
  2. Click on any of the options "iOS" or "Android"
  3. The flow will stay frozen. That is happening to all of my flows

I used those flows for months but after a payment problem with railway it was shut down. I redeployed it but it's clearly bugged.

Screen record of the error:
https://github.com/user-attachments/assets/f554cea5-9627-45e3-a44e-cc1bf173e4fb

Thanks!
@baptisteArno
Copy link
Owner

Can you provide the server logs? There should be a clear error there.

If you are self-hosting it with docker. Type this command in your terminal:

docker-compose logs

Paste all the logs here so that we can help you properly!

@meatboymeatboy
Copy link
Author

meatboymeatboy commented Sep 18, 2024 via email

@baptisteArno
Copy link
Owner

Indeed so it seems the migrations were not applied properly.... This is a tough one to fix.

It boils down to this: https://www.prisma.io/docs/orm/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute

You need to inspect your migrations table and see which one failed. Remove the associated row and rerun the app it should re-run the migration.

Baptiste.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@baptisteArno @meatboymeatboy and others