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

Closed
meatboymeatboy opened this issue Aug 26, 2024 · 7 comments
Closed

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

meatboymeatboy opened this issue Aug 26, 2024 · 7 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.

@panzer9
Copy link

panzer9 commented Oct 18, 2024 •
edited
Loading

Hello from a no code guy who admires the work you do with Typebot!

I guess I'm having the same issue. Just intalled a fresh Typebot with Easypanel and the "frozen button" issue keeps showing up.

I got the following logs from the DB.

Can you help @baptisteArno ?

(Here is a test bot published: https://chat.gustavobonato.com.br/test)

============

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

2024-10-18 03:43:54.163 UTC [49] LOG: received fast shutdown request
waiting for server to shut down....2024-10-18 03:43:54.164 UTC [49] LOG: aborting any active transactions
2024-10-18 03:43:54.168 UTC [49] LOG: background worker "logical replication launcher" (PID 56) exited with exit code 1
2024-10-18 03:43:54.168 UTC [51] LOG: shutting down
2024-10-18 03:43:54.183 UTC [49] LOG: database system is shut down
done
server stopped

PostgreSQL init process complete; ready for start up.

2024-10-18 03:43:54.293 UTC [7] LOG: starting PostgreSQL 13.16 (Debian 13.16-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-10-18 03:43:54.293 UTC [7] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-10-18 03:43:54.293 UTC [7] LOG: listening on IPv6 address "::", port 5432
2024-10-18 03:43:54.297 UTC [7] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-10-18 03:43:54.302 UTC [64] LOG: database system was shut down at 2024-10-18 03:43:54 UTC
2024-10-18 03:43:54.309 UTC [7] LOG: database system is ready to accept connections
2024-10-18 03:44:01.257 UTC [71] LOG: could not receive data from client: Connection reset by peer
2024-10-18 03:44:02.672 UTC [72] LOG: could not receive data from client: Connection reset by peer
2024-10-18 03:51:01.466 UTC [87] LOG: could not receive data from client: Connection reset by peer
2024-10-18 03:52:43.397 UTC [97] ERROR: column "createdAt" of relation "AnswerV2" does not exist at character 65
2024-10-18 03:52:43.397 UTC [97] STATEMENT: INSERT INTO "public"."AnswerV2" ("blockId","content","resultId","createdAt") VALUES ($1,$2,$3,$4)
2024-10-18 03:52:45.267 UTC [97] ERROR: column "createdAt" of relation "AnswerV2" does not exist at character 34
2024-10-18 03:52:45.267 UTC [97] STATEMENT: INSERT INTO "public"."AnswerV2" ("createdAt","blockId","resultId","content") VALUES ($1,$2,$3,$4)
2024-10-18 03:52:51.917 UTC [97] ERROR: column "createdAt" of relation "AnswerV2" does not exist at character 45
2024-10-18 03:52:51.917 UTC [97] STATEMENT: INSERT INTO "public"."AnswerV2" ("resultId","createdAt","content","blockId") VALUES ($1,$2,$3,$4)
2024-10-18 04:14:09.726 UTC [163] LOG: could not receive data from client: Connection reset by peer
2024-10-18 04:14:42.910 UTC [172] ERROR: column "createdAt" of relation "AnswerV2" does not exist at character 34
2024-10-18 04:14:42.910 UTC [172] STATEMENT: INSERT INTO "public"."AnswerV2" ("createdAt","blockId","resultId","content") VALUES ($1,$2,$3,$4)
2024-10-18 04:14:53.122 UTC [172] ERROR: column "createdAt" of relation "AnswerV2" does not exist at character 34
2024-10-18 04:14:53.122 UTC [172] STATEMENT: INSERT INTO "public"."AnswerV2" ("createdAt","content","blockId","resultId") VALUES ($1,$2,$3,$4)
2024-10-18 04:15:01.756 UTC [172] ERROR: column "createdAt" of relation "AnswerV2" does not exist at character 45
2024-10-18 04:15:01.756 UTC [172] STATEMENT: INSERT INTO "public"."AnswerV2" ("resultId","createdAt","blockId","content") VALUES ($1,$2,$3,$4)

@baptisteArno
Copy link
Owner

It was most likely an issue with the database migration.

Please see: https://www.prisma.io/docs/orm/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute

I can't help more than this 🙏

@baptisteArno baptisteArno closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2024
@panzer9
Copy link

panzer9 commented Oct 18, 2024

No problem! In the end, I managed to access the DB through DB Gate application, where I could manually add the "createdAt" column.

@kursku
Copy link

kursku commented Oct 31, 2024

No problem! In the end, I managed to access the DB through DB Gate application, where I could manually add the "createdAt" column.

How did you manually add the column? I'm struggling with it :(

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
6 participants
@kursku @baptisteArno @panzer9 @meatboymeatboy and others