No pieces showing

Need help
1

No Pieces Found in Admin Pieces config/ or user UI

We are trialling activepieces on self-hosted deployments, and are coming across the same issues on both a docker-compose install (remote, vm), and a docker-run install on my own local system.

When creating a fresh flow, or from template, no pieces show when loading.

no pieces showing in flow template
no pieces showing in flow template347×1141 27.7 KB

no pieces showing in pieces selection panel

When I attempt to manually add a piece by name (eg @activepieces/http) it says “Success” “Piece installed”, (ie no visible error is shown) but it still does not show in UI.

I have noticed in the dev console, that there are only HTTP 400 “Bad Request” errors when it is attempting to load individual pieces.
Bad requests in browser dev console

Things I have tried:

  • Updating to latest image
  • Running with specific pieces (docker run -d -p 8080:80 -v ~/.activepieces:/root/.activepieces -e AP_QUEUE_MODE=MEMORY -e AP_DB_TYPE=SQLITE3 -e AP_FRONTEND_URL="http://localhost:8080" -e AP_PIECES_SOURCE=FILE -e AP_DEV_PIECES=google-sheets,cal-com,slack,http activepieces/activepieces:latest)
  • Running without AP_DEV_PIECES
  • Running via docker compose, and docker run
  • Different browsers (no script blocking)

Any insight into this issue is greatly appreciated.

Thanks

2

Hi @finganinja , welcome to the community :star:

Do you have AP_PIECES_SOURCE=‘DB’ and AP_PIECES_SYNC_MODE=‘OFFICIAL_AUTO’ ?

If so just go to <instance_url>/platform/setup/pieces you should see a “sync pieces” button above the table to the right.

3

Hi Abdul,

Thank you for your response.

As per the run line above, AP_PIECES_SOURCE is set to FILE (default wasn’t working), but I will try DB explicitly and see if that changes anything.

I will also try AP_PIECES_SYNC_MODE=‘OFFICIAL_AUTO’.

I have tried sync pieces several times via the UI with no effect (no errors, but nothing changes - still no pieces shown)

4

Running with the command below worked to get pieces showing:
docker run -d -p 8080:80 -v ~/.activepieces:/root/.activepieces -e AP_QUEUE_MODE=MEMORY -e AP_DB_TYPE=SQLITE3 -e AP_FRONTEND_URL="http://localhost:8080" -e AP_PIECES_SOURCE=DB -e AP_PIECES_SYNC_MODE=OFFICIAL_AUTO activepieces/activepieces:latest

It was likely to be -e AP_PIECES_SOURCE=DB that rectified the problem, though I did not run with FILE to begin with - it was an attempt itself to fix the issue.
It would be good to know the technicalities behind why FILE doesn’t work, but it is good to know one way to fix the issue.

I think it would be a good idea to propagate sync/download errors on the server-side to the client, so that there isn’t a silent failure.

In any case, thanks again for your assistance.

1 Like
5

An addendum to this, for completeness:
The docker-compose instance had connectivity issues (firewall restrictions) when pulling piece data, so that issue was on our end.
In other words, both of our instance had issues that presented with the same symptom, but different causes.

1 Like
6

FILE is only mean for development, as in when you are developing a piece.

7

The distinction of FILE being used for developing pieces should probably be added to the environment variable description here (the term “development” is ambiguous without it - I read that as “developing workflows” that are not production-ready):
https://www.activepieces.com/docs/install/configuration/environment-variables#setting-piece-source

8

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.