Problem with API Workflow

Hi!. I have launched my website 1 day ago and I already reached my limit of workload in 1 hour. I know that the problem is because the Api workflow that it is in the website, but I dont know how to do it to decrease dramatically the number. So basically, the idea is that when I create a new task, the status of it will turn to “expired” once the due date is reached, if nobody has accepted it.
Could you help me to limit the amount of workloads to the minimun please?

Thanks!


At first glance it looks likes you have it scheduling itself, so it will explode in an exponential infinite loop. is that on purpose?

Button click → schedules workflow → workflow schedules itself on a list of things, each one of those will schedule another list of things → repeat :boom:

Thanks @tylerboodman! So deleting the step 2 in API Workflow expiredate will solve the problem?.
Is there a more efficient way to do this?

I’m not sure what Step 2 is doing, do you need it there?

I thought to run the workflow in a list of users, it would be needed. Only, I will need that in the due date, the workflow that change that specific task from request to expired is executed.

I’m not sure I’m following :sweat_smile:

Looks like you’re scheduling the workflow for when the Task expires. So looks like you do want to delete the Step 2 if it’s as simple as that

When the thing is created schedule a backend workflow to run on the things expiration date. That backend workflow will have one action to change status to expired.

If you expect date to be changed after creation, have data field to save original backend workflow id so it can be canceled when user changes the date and also schedule backend workflow again for new expiration date.

This topic was automatically closed after 70 days. New replies are no longer allowed.