BOT can reactivate itself?

[bolognesiedalla]

I've got a curiosity:
I set up a BOT that fires when I create a new record in the ACTIVITIES table.

Under certain conditions, the bot could create a new row in the ACTIVITIES table.

Now according to logic I would need it to be reactivated again in this case, but it doesn't seem to happen.... is it because it could end up in a sort of loop?

[Suvrutt_Gurjar]

---

@bolognesiedalla wrote:

Under certain conditions, the bot could create a new row in the ACTIVITIES table.

---

---

@bolognesiedalla wrote:

Now according to logic I would need it to be reactivated again in this case, but it doesn't seem to happen.

---

If you could elaborate the above two statements , then maybe community could suggest better?

[bolognesiedalla]

BOT - ACTIVITY table

1.adds the created task to your Google calendar.

2. If the task has already been completed, and if I need to meet this person again - create a new row in the ACTIVITIES table on the desired date.

The problem is that the future task (created in step 2) is not added to the Google calendar.
So I thought the Bot wouldn't wake up

[Suvrutt_Gurjar]

Thank you. I have yet to evaluate on feasibility but could you update your idea of how the app logic will know the following three attributes

---

---

@bolognesiedalla wrote:

If the task has already been completed,

---

and 

---

@bolognesiedalla wrote:

and if I need to meet this person again

---

---

and 

---

@bolognesiedalla wrote:

on the desired date.

---