simstudioai
Request timed out - Application loads but non-responsive canvas
Describe the bug Application does not respond to any interactions, and I cannot add any nodes or remove the initial trigger node.
To Reproduce Steps to reproduce the behavior:
- git clone project
- copy .env.sample file to parent directory of sim project
- replace postgres at the end of Database variable with "simstudio"
- add the 4 keys requested
- docker compose -f docker-compose.prod.yml up -d
- access the application
- Sign-up for new account
- login
- interface loads but non-responsive when trying to add or remove any items to canvas area
Expected behavior Ability to add new nodes to workflow and then execute.
Screenshots If applicable, add screenshots to help explain your problem. the migrations container does read exited everytime I try to run.
Additional context
Docker Logs:tacit@ubuntu:/media/storage/sim$ docker compose -f docker-compose.prod.yml logs -f
WARN[0000] The "COPILOT_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "SIM_AGENT_API_URL" variable is not set. Defaulting to a blank string.
migrations-1 | $ bunx drizzle-kit migrate --config=./drizzle.config.ts
migrations-1 | Reading config file '/app/packages/db/drizzle.config.ts'
migrations-1 | Using 'postgres' driver for database querying
realtime-1 | 2025-12-03T16:34:57.024Z WARN [Better Auth]: Social provider github is missing clientId or clientSecret
realtime-1 | 2025-12-03T16:34:57.024Z WARN [Better Auth]: Social provider google is missing clientId or clientSecret
migrations-1 | [⣷] applying migrations...{
migrations-1 | severity_local: "NOTICE",
migrations-1 | severity: "NOTICE",
migrations-1 | code: "42P06",
migrations-1 | message: "schema "drizzle" already exists, skipping",
migrations-1 | file: "schemacmds.c",
migrations-1 | line: "132",
migrations-1 | routine: "CreateSchemaCommand",
migrations-1 | }
migrations-1 | {
migrations-1 | severity_local: "NOTICE",
migrations-1 | severity: "NOTICE",
migrations-1 | code: "42P07",
migrations-1 | message: "relation "_drizzle_migrations" already exists, skipping",
migrations-1 | file: "parse_utilcmd.c",
migrations-1 | line: "207",
migrations-1 | routine: "transformCreateStmt",
migrations-1 | }
db-1 |
db-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
db-1 |
db-1 | 2025-12-03 16:34:48.742 UTC [1] LOG: starting PostgreSQL 16.11 (Debian 16.11-1.pgdg12+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit
db-1 | 2025-12-03 16:34:48.742 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
db-1 | 2025-12-03 16:34:48.742 UTC [1] LOG: listening on IPv6 address "::", port 5432
db-1 | 2025-12-03 16:34:48.748 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db-1 | 2025-12-03 16:34:48.758 UTC [29] LOG: database system was shut down at 2025-12-03 16:19:16 UTC
db-1 | 2025-12-03 16:34:48.773 UTC [1] LOG: database system is ready to accept connections
simstudio-1 | ▲ Next.js 15.4.1
simstudio-1 | - Local: http://localhost:3000
simstudio-1 | - Network: http://0.0.0.0:3000
simstudio-1 |
simstudio-1 | ✓ Starting...
simstudio-1 | ✓ Ready in 262ms
simstudio-1 | Accessing resource attributes before async attributes settled
simstudio-1 | Accessing resource attributes before async attributes settled
simstudio-1 | 2025-12-03T16:35:03.154Z WARN [Better Auth]: Social provider github is missing clientId or clientSecret
simstudio-1 | 2025-12-03T16:35:03.154Z WARN [Better Auth]: Social provider google is missing clientId or clientSecret
simstudio-1 | 2025-12-03T16:35:12.083Z WARN [Better Auth]: Social provider github is missing clientId or clientSecret
simstudio-1 | 2025-12-03T16:35:12.083Z WARN [Better Auth]: Social provider google is missing clientId or clientSecret
simstudio-1 | {"message":"Request timed out","stack":"Error: Request timed out\n at
also get the problem with pgvector version 17 that the db continues to shutdown:migrations-1 | message: "column "execution_data" of relation "workflow_execution_logs" already exists, skipping", db-1 | This user must also own the server process. db-1 | db-1 | The database cluster will be initialized with locale "en_US.utf8". db-1 | The default database encoding has accordingly been set to "UTF8". db-1 | The default text search configuration will be set to "english". db-1 | db-1 | Data page checksums are disabled. migrations-1 | file: "tablecmds.c", migrations-1 | line: "7471", migrations-1 | routine: "check_for_column_name_collision", migrations-1 | } migrations-1 | { db-1 | migrations-1 | severity_local: "NOTICE", migrations-1 | severity: "NOTICE", migrations-1 | code: "00000", migrations-1 | message: "column "metadata" of relation "workflow_execution_logs" does not exist, skipping", migrations-1 | file: "tablecmds.c", migrations-1 | line: "9019", migrations-1 | routine: "ATExecDropColumn", migrations-1 | } migrations-1 | { migrations-1 | severity_local: "NOTICE", migrations-1 | severity: "NOTICE", migrations-1 | code: "42622", migrations-1 | message: "identifier "workflow_log_webhook_delivery_subscription_id_workflow_log_webhook_id_fk" will be truncated to "workflow_log_webhook_delivery_subscription_id_workflow_log_webh"", migrations-1 | file: "scansup.c", migrations-1 | line: "99", migrations-1 | routine: "truncate_identifier", migrations-1 | } db-1 | fixing permissions on existing directory /var/lib/postgresql/data ... ok db-1 | creating subdirectories ... ok db-1 | selecting dynamic shared memory implementation ... posix db-1 | selecting default "max_connections" ... 100 db-1 | selecting default "shared_buffers" ... 128MB db-1 | selecting default time zone ... Etc/UTC db-1 | creating configuration files ... ok db-1 | running bootstrap script ... ok db-1 | performing post-bootstrap initialization ... ok db-1 | syncing data to disk ... ok db-1 | db-1 | db-1 | Success. You can now start the database server using: db-1 | db-1 | pg_ctl -D /var/lib/postgresql/data -l logfile start db-1 | db-1 | initdb: warning: enabling "trust" authentication for local connections db-1 | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. db-1 | waiting for server to start....2025-12-03 16:49:12.600 UTC [48] LOG: starting PostgreSQL 17.7 (Debian 17.7-3.pgdg12+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit db-1 | 2025-12-03 16:49:12.603 UTC [48] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" db-1 | 2025-12-03 16:49:12.615 UTC [51] LOG: database system was shut down at 2025-12-03 16:49:11 UTC db-1 | 2025-12-03 16:49:12.628 UTC [48] LOG: database system is ready to accept connections db-1 | done db-1 | server started db-1 | CREATE DATABASE db-1 | db-1 | db-1 | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/* db-1 | db-1 | 2025-12-03 16:49:12.866 UTC [48] LOG: received fast shutdown request db-1 | waiting for server to shut down....2025-12-03 16:49:12.869 UTC [48] LOG: aborting any active transactions db-1 | 2025-12-03 16:49:12.872 UTC [48] LOG: background worker "logical replication launcher" (PID 54) exited with exit code 1 db-1 | 2025-12-03 16:49:12.875 UTC [49] LOG: shutting down db-1 | 2025-12-03 16:49:12.878 UTC [49] LOG: checkpoint starting: shutdown immediate db-1 | 2025-12-03 16:49:13.124 UTC [49] LOG: checkpoint complete: wrote 921 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.025 s, sync=0.208 s, total=0.250 s; sync files=301, longest=0.003 s, average=0.001 s; distance=4238 kB, estimate=4238 kB; lsn=0/1908958, redo lsn=0/1908958 db-1 | 2025-12-03 16:49:13.153 UTC [48] LOG: database system is shut down db-1 | done db-1 | server stopped db-1 | db-1 | PostgreSQL init process complete; ready for start up. db-1 | db-1 | 2025-12-03 16:49:13.201 UTC [1] LOG: starting PostgreSQL 17.7 (Debian 17.7-3.pgdg12+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit db-1 | 2025-12-03 16:49:13.201 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 db-1 | 2025-12-03 16:49:13.201 UTC [1] LOG: listening on IPv6 address "::", port 5432 db-1 | 2025-12-03 16:49:13.207 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" db-1 | 2025-12-03 16:49:13.215 UTC [64] LOG: database system was shut down at 2025-12-03 16:49:13 UTC db-1 | 2025-12-03 16:49:13.223 UTC [1] LOG: database system is ready to accept connections