Issue Description: Upon starting the Activepieces Docker container, I receive an ENTITY_NOT_FOUND error with details indicating piece_metadata_not_found for a project ID. This occurs in a fresh Docker setup without any direct interaction or modification of the data or configurations on my part.
Steps Taken:
Stopped and removed the existing Activepieces container.
Removed the Activepieces Docker image and pulled the latest version.
Ran the container with the standard setup instructions, ensuring the correct mapping of the ~/.activepieces directory to persist data.
The error persists even after these steps, indicating a potential issue with the initialization process or a bug.
System Environment:
Docker version: (include your Docker version here)
Host OS: (include your OS and version here)
Activepieces version: Latest from Docker Hub as of (include date here)
Error Logs:
{“level”:50,“time”:1712296997302,“pid”:7,“hostname”:“15c34f980f47”,“err”:{“type”:“ActivepiecesError”,“message”:“ENTITY_NOT_FOUND”,“stack”:“Error: ENTITY_NOT_FOUND\n at Object. (/usr/src/app/dist/packages/server/api/main.js:1:717932)\n at Generator.next ()\n at fulfilled (/usr/src/app/dist/packages/server/api/node_modules/tslib/tslib.js:166:62)”,“error”:{“code”:“ENTITY_NOT_FOUND”,“params”:{“message”:“piece_metadata_not_found projectId=wjCkOa7ifnpyuj6qe4vrv”}}},“msg”:“[Main#main]”}
Given these details, I’m seeking guidance on how to resolve this error or any insights into potential causes. I’ve ensured that my system meets all prerequisites for Activepieces and followed the installation instructions precisely. I’m curious if anyone else has encountered a similar issue or if there are known bugs or workarounds that I might not be aware of.
Any assistance or suggestions from the community would be greatly appreciated. Thank you for your time and support.
Thanks for your help. I’ve already reinstalled the server and made a whole new installation. I encounter an issue there as well, but I will create a seperate topic for that.
The same it happened to me, my installation was setup using PULUMI before 7-8 months ago… and suddenly without any “touch” it went down… its 4 days now showing the same error:
{“level”:50,“time”:1712598809311,“pid”:8,“hostname”:“ip-10-0-215-124.ec2.internal”,“err”:{“type”:“ActivepiecesError”,“message”:“ENTITY_NOT_FOUND”,“stack”:“Error: ENTITY_NOT_FOUND\n at Object. (/usr/src/app/dist/packages/server/api/main.js:1:717932)\n at Generator.next ()\n at fulfilled (/usr/src/app/dist/packages/server/api/node_modules/tslib/tslib.js:166:62)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)”,“error”:{“code”:“ENTITY_NOT_FOUND”,“params”:{“message”:“piece_metadata_not_found projectId=q0HOP8ezk4YJbAiSspbp2”}}},“msg”:“[Main#main]”}
I think its an update released from AP … and it Auto Updated.
{“level”:50,“time”:1712687144725,“pid”:8,“hostname”:“ip-10-0-200-209.ec2.internal”,“err”:{“type”:“ActivepiecesError”,“message”:“SYSTEM_PROP_INVALID: System property AP_ENCRYPTION_KEY must be defined”,“stack”:“Error: SYSTEM_PROP_INVALID: System property AP_ENCRYPTION_KEY must be defined\n at /usr/src/app/dist/packages/server/api/main.js:1:249962\n at Generator.next ()\n at /usr/src/app/dist/packages/server/api/node_modules/tslib/tslib.js:169:75\n at new Promise ()\n at Object.__awaiter (/usr/src/app/dist/packages/server/api/node_modules/tslib/tslib.js:165:16)\n at t.loadEncryptionKey (/usr/src/app/dist/packages/server/api/main.js:1:249681)\n at /usr/src/app/dist/packages/server/api/main.js:1:7950\n at Generator.next ()\n at /usr/src/app/dist/packages/server/api/node_modules/tslib/tslib.js:169:75\n at new Promise ()”,“error”:{“code”:“SYSTEM_PROP_INVALID”,“params”:{“prop”:“ENCRYPTION_KEY”}}},“msg”:“[Main#main]”}
The AP_ENCRYPTION_KEY is missing from your environment variables. Please use sh tools/deploy.sh; it should generate all the environment variables you need.