@NerdJam you get it right! . New exciting announcements... but not for you early adopter!

Is there anyone here to help with my piece issue?

I created a much needed delay by queue piece i want to put out to the community. It rate limits flows. You simply name the queue and select your time interval seconds, minutes, hours. So if you have 50 flows run at once and hit this step they will all go to que and the piece will release one at a time based on the interval set

I cant get it out to the community i dont have api access and the instructions online are not so clear and there are no tutorials to publish. Putting it in npm doesnt help with when the docker image is built

And no this is not the same as the current que piece as its currently an issue that you can add to que and then have to run another step to pull from que this does not solve rate issues. If 50 steps hit current que and delays for 1 minute then all 50 will pull from que after the 1 minute. My delay after que piece solves this issue and provides utility to the community

https://www.activepieces.com/docs/developers/building-pieces/create-action https://www.activepieces.com/docs/developers/sharing-pieces/contribute

Did this didnt work. My piece does not appear in the builder even after installing and running the docker build.

Cant contribute i do not have an api key. I just put it in npm

@drhomes/pieces-delay-after-queue

You need to open pull request in GitHub then the Activepieces team will confirm.

Once the pull request is approved, it will be merged into the main branch. Your piece will be available within a few minutes. An automatic GitHub action will package it and create an npm package on npmjs.com.

Does it matter i have a modified fork?

I think you did all right, you need to modify fork then open pull request, if there will be any problem they will write you (in pull request)

The point is that you modify the fork, otherwise there is no point in opening a pull request because there is no change.

I did publish it on npm @drhomes/piece-delay-after-queue

I just find it strange i built a piece in the software and installed it and for some reason the software doesnt show the pieces the users built. Just doesnt make since why the feature would even be in the software if the user cant built it with their docker

No you don’t need to do it, just open request then when they will approve npm package will be created automatically

When they approve the request in any self hosted platform will be shown your changes

Any update about the announced restrictions launched a few days ago?

Hey guys, beginner's question here: - How can I use the "`Delay Until`" piece for appointment reminders? E.G.: I have a dynamic value

[appointment.date_time]

, and I want to wait until 24h before the

[appointment.date_time]

(to then send an email). Is it doable with "Delay"? https://cdn.discordapp.com/attachments/1053778461275201576/1393616413712847013/Screenshot_2025-07-12_at_16.29.34.png?ex=6873d1ed&is=6872806d&hm=097d3fe6e7c87983e74dcd0a69584d6dcf48a643c76b81ab427bb25dc1f42a0c&

I can't find it on pm

Nvm I do now https://www.npmjs.com/@drhomes/piece-delay-after-queue

It seems working i installed it https://cdn.discordapp.com/attachments/1053778461275201576/1393682184707248138/image.png?ex=68740f2e&is=6872bdae&hm=752f5176d0732618c60c24911b342c8496f781cbf4c1fe360f48798ef98aa1a7&

Yes im trying to build it with my image not have to manually pull it

Im not sure how to publish it to the community to be used in the main repo

My whole active pieces system is customized and self hosted so pushing my code wouldnt work so well with the main repo.

Is someone in the community ever to take it from npm and publish it for the community?

You can use custom code for creating new date // change with your appointment.date_time let now = new Date(); // Now we are creating new date let futureDate = new Date(now.getTime() + 24 * 60 * 60 * 1000); // Then just return futureDate

Hi guys, I cannot test MCP triggers in new flows anymore. The spinner just spins indefinitely. I tried different browsers. There are no errors in the console. In pre-existing flows, however, it works fine and I can test the MCP trigger again. This is pretty annoying because I cannot set up new flows like this. Any ideas? Thanks!