While there are simple solutions using the GraphQL API, this too should be possible in “raw” Pipefy only.

I imagine the following components:

• Use the “users can only edit cards they are assigned to” authentication requirement in the Task pipe to solve the “prevent more than one worker working on a task at the same time”
• Use an assignee field to select the one worker that is to be working on this task
• For the workers to assign themselves, use a connected field to a connected pipe (“Worker-Distribution”, e.g.)
• In the Task-Pipe, create a Worker-Distribution connected card with the E-Mails of the possible workers and an assignee field
• When this conneccted card is created, send the E-Mail to the workers
• The worker who responds first, assignes itself to the Distribution Card using said assignee field
• Use a conditional to hide this assignee field in the Distribution Card to prevent other workers from assigning themselves
• Fill the assignee field of the parent, Task Card based on the assignee of the Distribution Card, using an automation.

I can imagine other ways, e.g. using public forms with only the assignee field etc.

Good luck!

Hello @skip, 

I our company we have pipeline, where each one is a phase, than when we get a new task someone have to claim it in 24h, it works very well for small groups.

Hi!
Will the new feature below resolve this issue?

I believe Round Robin will be the best option! So all users will have a different card, and it will not allow 2 users to work on the same task!

Perfect!

Tks!

Good!