I am sure that I have the pretty much the same issue as the last question posted here. Since February 18, every IFTTT applet with the trigger "Advanced: Custom Salesforce Trigger [package required]" has malfunctioned. I have to go to IFTTT and make manual checks, which work only sporadically. So far, here's what I gathered of my predicament:
- IFTTT's Apex classes and triggers remain valid up to the time of this post.
- Flows creating IFTTT events work on Salesforce's side. IFTTT events are inserted on Salesforce's side, there is seemingly a callout to IFTTT, but it says "There is a problem with this trigger" on IFTTT's side.
- That trigger works sporadically, and that requires manual checks. Very often, it does not even work, with an error message saying that "There is a problem checking this Applet".
- IFTTT's remote logins are successful.
- Occasionally, when I try to reconnect to Salesforce from IFTTT, I get redirected to a Heroku page, which says "Oops, an error occurred. This exception has been logged with ID something."
- I have version 1.8 of the package, and cannot downgrade to version 1.7.
- Other IFTTT applets that do not rely on that trigger work fine.
- IFTTT's Salesforce action "Advanced: Insert a Record" works. The (less useful) trigger "Record Created or Updated" also works. I haven't tested IFTTT's ability to query Salesforce records, though.
- IFTTT's Remote Site Setting is active. Disabling Protocol Security has no effect.
I'm sure that it's not just me who's affected; about 50% of API calls to IFTTT around the globe seem to fail. Would you kindly investigate the issue?
1 réponse
It has been 4 days after the original post. I am quite certain that this happens worldwide.
I look forward to a reply. Thank you.
