Confiforms IFTTT Trigger onCreated not firing
Asked by Jane Smith:

Hi, I have an IFTTT trigger that isn't firing despite meeting conditions.

We have a service database that accepts requests and sets the status to **ACCEPTED** should it meet specific conditions.

Here is an example below. If the submission due date is at least 3 weeks from today's date, then set status to **ACCEPTED**.

**Event**

```
onCreated
```

**Choose Action to perform**

```
Create / Update ConfiForms Entry
```

**Fire IFTTT action only when this condition/filter is met**

```
date:>=([entry._today.add(1814400000)])
```

**Parameters to set on the entry**

```
 entryId=[entry.id]&status=success
```

We've have different date criteria but overall the same layout for IFTTT triggers. I've noticed lately that this does not always trigger properly, though there was no issues in the past. For example, if we submit a request for sometime in March, the record will be recorded but the status does not update to **ACCEPTED**, and therefore, the relational IFTTT email trigger does not fire (this email lets the team know there's been a new submission and is fired onModified).

There are 3 actions that are not firing:

1. Update status to ACCEPTED (onCreated)

2. Send submitter a confirmation email (onCreated)

3. Send team notice email (onModified (from onCreated parameters set on the entry))

Other criteria for onCreated include a status set to **DECLINED** should the request fail to meet criteria. The expected actions for **DECLINED**are the same as above.

Any idea why this could be happening? Is it in relation to the date (farfetched, but is the due date too far out)?


Answers:
author: Alex Medved _ConfiForms_
body: Hi

Hard to tell without seeing complete configuration, but you can check which IFTTTs and in what order get executed

<https://wiki.vertuna.com/display/CONFIFORMS/How+to+troubleshoot+and+debug+ConfiForms+IFTTT+rules+execution>

This should help you to understand what is going on

You can also open a [ticket with us](https://wiki.vertuna.com/display/VERTUNA/Support+Request+Form)

Although we cannot debug and design forms for customers we can look into specific issues to see if there is some misconfiguration or something like that which can be spotted and fixed

Alex

comments: author: Jane Smith
body: Thanks, [@Alex Medved _ConfiForms_](/t5/user/viewprofilepage/user-id/781630) I am reaching out to our Admin team to see if they can allow the debug feature. Is it possible that our page is growing too large with records? It's interesting that it all of a sudden stopped working when it was fine just a couple weeks ago. I've also created a duplicate of the form and all functions are working as intended.


author: Alex Medved _ConfiForms_
body: What we have seen is that most often the email server response times or/and availability could be the cause of lots of drama

Dont know how those IFTTTs are configured, but consider using the Confluence email queue (option in the macro parameters).

But again, having a debug enabled will show you what IFTTTs were executed, in which order and execution time. This is really the best advise I can give (or to open a support ticket with us, sharing a complete configuration of the form, so we can have a look and try to help)

Alex


Tags: confiforms

confluence-server

server