looping of the planned task

So, you react upon user registration (insert user entity) and schedule a task for later processing. That looks OK, what's your question though?

I need to continue postponing the task after it has been done for the first time.

So, how about scheduling a new task then?

So I was thinking about it, but will the correct queue of scheduled tasks be created

Well, why not. When you schedule a task, it goes into the queue to be processed when the schedule is due. It doesn't matter from where the task gets scheduled. At least, it shouldn't. Doesn't hurt to just give it a try.

Hello, the task couldn't be resolved successfully. Queue creation is not functioning; tasks are executing simultaneously.

Can you provide more details, please? With the given information, there isn't anything we can do.

Of course, I have attached a photo

I'm really sorry, I hope to not asking too much. But to get free support in solving your own use cases, it would really be necessary to provide us with data that we can quickly reproduce and test. So, you should create the most simple model that helps you to demonstrate the issue. Then you can export that model and upload it here, together with an explanation of what the model should do and at which step it failed. Before that, you should also use the debugging described at https://ecaguide.org/eca/debugging/ and copy the debugging output here as well to show, what the issue was at the point where the model didn't do what you expected.

I have created a simple ECA (Event-Condition-Action) model to visually understand my task. I need nodes to be created after a user registers, and then I need nodes for this user to continue being created during the run cron. In other words, this is the loop I am referring to.

Well, it's really hard to provide support under these circumstances. While I can load the uploaded model, there is no labels or annotations in there. This is then time consuming to click through all the components to see what they're doing. Please, please, please, if you want support, help us with more details.

Also, your description doesn't really describe the steps in detail what's happening and at what step it fails. It also doesn't contain any debugging information, which I expect you to go through first, before expecting someone else (=us) to spend that time to help you solcing your problem.

I then looked through the model and see that you haven't tried what I recommended above in #4 and #6. You have implemented a cron job which runs every minute and adds a new task to the queue every minute. That should then process those tasks, again every minute.

What I suggested was, that you "Insert user" is scheduling a task, which is OK. And when that task is being executed, it can then add another task to the queue when it got completed. You don't need a cron to re-schedule your task.

I noticed points #4 #6, and everything started working. I apologize for the time you spent on this.

Glad, it's resolved.

Automatically closed - issue fixed for 2 weeks with no activity.