Skip to main content
replaced http://drupal.stackexchange.com/ with https://drupal.stackexchange.com/
Source Link

Is there a way to delay the execution of the actions so the node is actually created already?

Yes, you need to enable the Rules Shecheduler module (comes with rules).

Then Create a Rule Component that will do your action.

Then create a rule with action of schedule component. (set it to 5 mins)

For example, see Rules Conditions being evaluated after schedule time elapsed?Rules Conditions being evaluated after schedule time elapsed?

Attention:

Be aware that the actual trigger will only happen the next time your Cron job runs. So if you say "after 5 mins", and the next Cron job runs in say about an hour, then it'll only be after about an hour. If that's not acceptable (as was the case in this question), then you'd have to run your cron job like every 5, 10 or 15 minutes.

So I suggest using Ultimate Cron, that way you can target, so that only your rule cron job runs every 5 or x mins, instead of running every single cron job.

In other words, it allows you to run different catagories/module cron jobs at different times. While you could run less crucial jobs, like Update Manager, only once a day (every 24 hours).

enter image description here

Is there a way to delay the execution of the actions so the node is actually created already?

Yes, you need to enable the Rules Shecheduler module (comes with rules).

Then Create a Rule Component that will do your action.

Then create a rule with action of schedule component. (set it to 5 mins)

For example, see Rules Conditions being evaluated after schedule time elapsed?

Attention:

Be aware that the actual trigger will only happen the next time your Cron job runs. So if you say "after 5 mins", and the next Cron job runs in say about an hour, then it'll only be after about an hour. If that's not acceptable (as was the case in this question), then you'd have to run your cron job like every 5, 10 or 15 minutes.

So I suggest using Ultimate Cron, that way you can target, so that only your rule cron job runs every 5 or x mins, instead of running every single cron job.

In other words, it allows you to run different catagories/module cron jobs at different times. While you could run less crucial jobs, like Update Manager, only once a day (every 24 hours).

enter image description here

Is there a way to delay the execution of the actions so the node is actually created already?

Yes, you need to enable the Rules Shecheduler module (comes with rules).

Then Create a Rule Component that will do your action.

Then create a rule with action of schedule component. (set it to 5 mins)

For example, see Rules Conditions being evaluated after schedule time elapsed?

Attention:

Be aware that the actual trigger will only happen the next time your Cron job runs. So if you say "after 5 mins", and the next Cron job runs in say about an hour, then it'll only be after about an hour. If that's not acceptable (as was the case in this question), then you'd have to run your cron job like every 5, 10 or 15 minutes.

So I suggest using Ultimate Cron, that way you can target, so that only your rule cron job runs every 5 or x mins, instead of running every single cron job.

In other words, it allows you to run different catagories/module cron jobs at different times. While you could run less crucial jobs, like Update Manager, only once a day (every 24 hours).

enter image description here

Integrate comment from OPer
Source Link
Pierre.Vriens
  • 36k
  • 40
  • 50
  • 182

Is there a way to delay the execution of the actions so the node is actually created already?

Yes, you need to enable the Rules Shecheduler module (comes with rules).

Then Create a Rule Component that will do your action.

Then create a rule with action of schedule component. (set it to 5 mins)

For example, see Rules Conditions being evaluated after schedule time elapsed?

Attention:

Be aware that the actual trigger will only happen the next time your Cron job runs. So if you say "after 5 mins", and the next Cron job runs in say about an hour, then it'll only be after about an hour. If that's not acceptable (as was the case in this question), then you'd have to run your cron job like every 5, 10 or 15 minutes.

So I suggest using Ultimate Cron, that way you can target, so that only your rule cron job runs every 5 or x mins, instead of running every single cron job.

In other words, it allows you to run different catagories/module cron jobs at different times. While you could run less crucial jobs, like Update Manager, only once a day (every 24 hours).

enter image description here

Is there a way to delay the execution of the actions so the node is actually created already?

Yes, you need to enable the Rules Shecheduler module (comes with rules).

Then Create a Rule Component that will do your action.

Then create a rule with action of schedule component. (set it to 5 mins)

For example, see Rules Conditions being evaluated after schedule time elapsed?

Attention:

Be aware that the actual trigger will only happen the next time your Cron job runs. So if you say "after 5 mins", and the next Cron job runs in say about an hour, then it'll only be after about an hour. If that's not acceptable (as was the case in this question), then you'd have to run your cron job like every 5, 10 or 15 minutes.

So I suggest using Ultimate Cron, that way you can target, so that only your rule cron job runs every 5 or x mins, instead of running every single cron job.

In other words, it allows you to run different catagories/module cron jobs at different times.

enter image description here

Is there a way to delay the execution of the actions so the node is actually created already?

Yes, you need to enable the Rules Shecheduler module (comes with rules).

Then Create a Rule Component that will do your action.

Then create a rule with action of schedule component. (set it to 5 mins)

For example, see Rules Conditions being evaluated after schedule time elapsed?

Attention:

Be aware that the actual trigger will only happen the next time your Cron job runs. So if you say "after 5 mins", and the next Cron job runs in say about an hour, then it'll only be after about an hour. If that's not acceptable (as was the case in this question), then you'd have to run your cron job like every 5, 10 or 15 minutes.

So I suggest using Ultimate Cron, that way you can target, so that only your rule cron job runs every 5 or x mins, instead of running every single cron job.

In other words, it allows you to run different catagories/module cron jobs at different times. While you could run less crucial jobs, like Update Manager, only once a day (every 24 hours).

enter image description here

added 90 characters in body
Source Link
No Sssweat
  • 31.6k
  • 14
  • 55
  • 91

Is there a way to delay the execution of the actions so the node is actually created already?

Yes, you need to enable the Rules Shecheduler module (comes with rules).

Then Create a Rule Component that will do your action.

Then create a rule with action of schedule component. (set it to 5 mins)

For example, see Rules Conditions being evaluated after schedule time elapsed?

Attention:

Be aware that the actual trigger will only happen the next time your Cron job runs. So if you say "after 5 mins", and the next Cron job runs in say about an hour, then it'll only be after about an hour. If that's not acceptable (as was the case in this question), then you'd have to run your cron job like every 5, 10 or 15 minutes.

So I suggest using Ultimate Cron, that way you can target, so that only your rule cron job runs every 5 or x mins, instead of running every single cron job.

In other words, it allows you to run different catagories/module cron jobs at different times.

enter image description here

Is there a way to delay the execution of the actions so the node is actually created already?

Yes, you need to enable the Rules Shecheduler module (comes with rules).

Then Create a Rule Component that will do your action.

Then create a rule with action of schedule component. (set it to 5 mins)

For example, see Rules Conditions being evaluated after schedule time elapsed?

Attention:

Be aware that the actual trigger will only happen the next time your Cron job runs. So if you say "after 5 mins", and the next Cron job runs in say about an hour, then it'll only be after about an hour. If that's not acceptable (as was the case in this question), then you'd have to run your cron job like every 5, 10 or 15 minutes.

So I suggest using Ultimate Cron, that way you can target, so that only your rule cron job runs every 5 or x mins, instead of running every single cron job.

Is there a way to delay the execution of the actions so the node is actually created already?

Yes, you need to enable the Rules Shecheduler module (comes with rules).

Then Create a Rule Component that will do your action.

Then create a rule with action of schedule component. (set it to 5 mins)

For example, see Rules Conditions being evaluated after schedule time elapsed?

Attention:

Be aware that the actual trigger will only happen the next time your Cron job runs. So if you say "after 5 mins", and the next Cron job runs in say about an hour, then it'll only be after about an hour. If that's not acceptable (as was the case in this question), then you'd have to run your cron job like every 5, 10 or 15 minutes.

So I suggest using Ultimate Cron, that way you can target, so that only your rule cron job runs every 5 or x mins, instead of running every single cron job.

In other words, it allows you to run different catagories/module cron jobs at different times.

enter image description here

Refine Attention parg
Source Link
Pierre.Vriens
  • 36k
  • 40
  • 50
  • 182
Loading
added 571 characters in body
Source Link
No Sssweat
  • 31.6k
  • 14
  • 55
  • 91
Loading
added 18 characters in body
Source Link
No Sssweat
  • 31.6k
  • 14
  • 55
  • 91
Loading
Source Link
No Sssweat
  • 31.6k
  • 14
  • 55
  • 91
Loading