BEAR
08/31/2026, 10:44 AMKel
08/31/2026, 11:03 AMitpromike
09/01/2026, 10:12 PMitpromike
09/01/2026, 10:13 PMreach
09/02/2026, 2:22 PMitpromike
09/02/2026, 6:33 PMAfolabi
09/03/2026, 9:48 AMJOHNSON
09/04/2026, 12:25 AMjoeworkman
09/04/2026, 2:52 AMpiece not found error for the bettermode piece? what happened?
{
"__apErrorVersion": 1,
"message": "{\n \"message\": \"Piece not found for package: @activepieces/piece-bettermode-0.1.6\"\n}",
"errorName": "PieceNotFoundError",
"raw": "V [PieceNotFoundError]: {\n \"message\": \"Piece not found for package: @activepieces/piece-bettermode-0.1.6\"\n}\n at Object.getPiecePath (/root/common/main.js:104:31626)\n at async /root/common/main.js:104:29853\n at async mt (/root/common/main.js:63:4189)\n at async Object.tryCatchAndThrowOnEngineError (/root/common/main.js:103:86748)\n at async Object.loadPieceOrThrow (/root/common/main.js:104:29736)\n at async Object.getPieceAndActionOrThrow (/root/common/main.js:104:30502)\n at async /root/common/main.js:104:42972\n at async mt (/root/common/main.js:63:4189)\n at async Object.tryCatchAndThrowOnEngineError (/root/common/main.js:103:86748)\n at async YM (/root/common/main.js:104:42806) {\n cause: undefined,\n type: 'ENGINE'\n}"
}Phantom
09/04/2026, 11:40 AMAaron
09/04/2026, 12:14 PMsepiol026
09/05/2026, 10:25 AMHD99
09/06/2026, 9:14 AMMissing tiktoken_bg.wasm at .../piece-openai/src/index.js:7:533218
- HTTP piece: Request with GET/HEAD method cannot have body
Questions:
1. Why can a newer piece version break older versions that were previously working? Is there a way to get notified in advance when a piece version we're using is being deprecated, so we can upgrade proactively instead of discovering it via failures in production?
2. Is there a way to enable automatic upgrades for pieces (globally or per-piece), instead of having to manually upgrade each one individually?
3. Is there a way to set up better alerting or export run telemetry (e.g., to Grafana/Prometheus) so we can build our own dashboards and alerts? This would help us catch issues like this one much earlier next time.
Thanks in advance for any guidance!Bastien
09/07/2026, 7:54 AMmorty
09/07/2026, 1:27 PM{{ process.env }} works in Mapping expressions.
After upgrading to 0.90.2, it returns an empty value, while process.env still works correctly in Code pieces.
Environment variables are explicitly configured via:
env
AP_SANDBOX_PROPAGATED_ENV_VARS=MY_API_KEY,...
Behavior:
* Code: process.env.MY_API_KEY → ✅ works
* Mapping: {{ process.env.MY_API_KEY }} → ❌ empty
* Mapping: {{ process.env }} → ❌ empty
* Mapping: {{ process['env'] }} → ❌ empty
* v0.77.8 → Mapping access worked
There are many places in my flows that directly use expressions like {{ process.env.MY_API_KEY }}. Is there a quick way to fix this without modifying the flows?
Is this an intentional change in the Expression/Mapping evaluator, or a regression in v0.90.2? Is there a configuration to restore access to the propagated environment variables in Mapping expressions?Chaker
09/07/2026, 1:41 PM{{ process.env.X || '' }}morty
09/07/2026, 2:17 PMstep_x refers to when using the Mapping piece or similar pieces. This makes it much harder to work with flows that have many steps.joeworkman
09/07/2026, 3:54 PMsendy completely stopped working recently. It took me a long time to figure out if I moved to v0.1.4 then it worked again. It looks like it got bumped to v0.1.5 and then v0.1.6 through some automated changes. I have no clue what is different between the versions. Can someone help figure it out? It could be a wider issue that was cuased by these automated bumps?sidd3024
09/09/2026, 7:44 PMAlisonAguiar
09/10/2026, 2:42 AMNotMy_RealName
09/11/2026, 3:46 PMAakanksha Mourya
09/11/2026, 4:41 PMsepiol026
09/13/2026, 9:14 AMMiniSpecter
09/14/2026, 2:45 AMkrnshrm
09/14/2026, 8:12 AMBharat Karavadra
09/16/2026, 1:53 PMVaibhav1000
09/17/2026, 2:09 PMitpromike
09/17/2026, 8:18 PMitpromike
09/17/2026, 8:19 PM