Confiforms IFTTT Trigger onCreated not firing

Question

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)?

Alex Medved _ConfiForms_ · Answer

Hi @Jane Smith

I suggest to move the logic of setting the value for the restricted status field to ConfiForms IFTTT

Basically setting it to update the field conditionally via this IFTTT rule (one for each case - pending/declined) and this IFTTT needs to be set (via the macro parameter) to bypass field permissions and restrictions

This way you will be able to modify the restricted field

Alex

Jane Smith_m7slch · Answer

Hi @Alex Medved _ConfiForms_ revisiting this thread. I believe this wasn't a server issue, but rather the way my Confiform was setup.

We have the STATUS field to be automatically set to PENDING or DECLINED onCreated. In-line Edits are enabled for ease of updating for the team. The entry.user is also able to edit their record if they want to update information. However, we do not want the entry.user to be able to update the STATUS, so the STATUS was Editable only by group "REVIEWERS". Because it was only editable by group REVIEWERS, the IFTTT to update the STATUS onCreated was not firing. By disabling the editable only by group REVIEWERS, the STATUS has been successfully firing. The issue is now entry.user can update the STATUS. How can I approach this where the entry.user cannot update the STATUS but the IFTTT will still trigger?

Alex Medved _ConfiForms_ · Answer

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