# How to save "running jobs"

**URL:** <https://discourse.nodered.org/t/how-to-save-running-jobs/36869>\
**Category:** General\
**Created:** [2 December 2020 12:33 UTC](https://discourse.nodered.org/t/how-to-save-running-jobs/36869 "2020-12-02T12:33:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![flow3000](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@flow3000](https://discourse.nodered.org/u/flow3000)\
**Post date:** [2 December 2020 12:33 UTC](https://discourse.nodered.org/t/how-to-save-running-jobs/36869/1 "2020-12-02T12:33:54Z")

</div>

Hi,

I currently working on a http API.

The API sends emails after some given time (immedialety, after 3 days, after 14 days, etc....).

Question 1:

- From your experience, how many "delayed jobs" can Node Red handle befor it "crashes".

Question 2:

- What about a server restart? From what I know, running or delayed jobs got lost when Node Red stops.

Is there a "addon" that saves the current position for all jobs inside a text file or database?

Kind regards!

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [2 December 2020 13:57 UTC](https://discourse.nodered.org/t/how-to-save-running-jobs/36869/2 "2020-12-02T13:57:23Z")

</div>

How are you scheduling the jobs for later action?  
Node red should not crash unless there is a bug or you run out of memory.

The answer to question 2 depends on how you are scheduling them.

---

<div class="post-metadata">

**Author:** ![flow3000](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@flow3000](https://discourse.nodered.org/u/flow3000)\
**Post date:** [2 December 2020 14:03 UTC](https://discourse.nodered.org/t/how-to-save-running-jobs/36869/3 "2020-12-02T14:03:47Z")

</div>

For scheduling I use the **delay node**.  
Its state wont get saved right?

I thought that there might be a way to save the current "state" of a node - So that after a restart of node red, the delay node still knows for how long it is active.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [2 December 2020 14:06 UTC](https://discourse.nodered.org/t/how-to-save-running-jobs/36869/4 "2020-12-02T14:06:34Z")

</div>

> [@flow3000](#):
>
> For scheduling I use the **delay node**.

I suggest that is a bad idea. Instead use Persistent Context to save what needs to be done and when, and then have a simple flow that does it when necessary. [Working with context : Node-RED](https://nodered.org/docs/user-guide/context)

---

<div class="post-metadata">

**Author:** ![flow3000](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@flow3000](https://discourse.nodered.org/u/flow3000)\
**Post date:** [2 December 2020 14:08 UTC](https://discourse.nodered.org/t/how-to-save-running-jobs/36869/5 "2020-12-02T14:08:58Z")

</div>

Ah, I see. That seems to be what I was looking for.

Thank you 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [31 January 2021 14:09 UTC](https://discourse.nodered.org/t/how-to-save-running-jobs/36869/6 "2021-01-31T14:09:01Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.