Inbound email action weird behavior and target record is empty even when the email log shows processed and incident created.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2022 12:43 AM
I have created an Inbound action on incident table. I want that once the condition meets and this inbound action run, no other should run after that. So I checked stop processing.
Issue: 1. If I check stop processing then the email log shows the correct inbound action name being processed and also shows an incident number but the target record is empty on email and no such incident is available in incident table.
Issue 2: If I don't check stop processing, my inbound action runs and shows processed with an incident number but then it gets overridden by other inbound action and I see that incident created from other inbound action.
How come email log shows processed and incident number but no incident is there? How to resolve this, please suggest.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2022 06:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2022 06:38 AM
It would likely help if you posted the conditions and the code of your inbound action for others to review when asking a question like this, as there are many potential issues that could be at fault.
Generally speaking:
Make sure your inbound action has a current.insert() statement at the end and make sure it is accessible (not inside an if/then/else that you are never reaching). That's one of the most common points of failure. Add gs.info() statements and make sure your code is executing the way you think it is.
You might also consider using a Flow with an inbound email trigger instead of an inbound action, unless you are having to do some heavy custom scripting in your action. The drag and drop for record creation is a nice feature, and as a bonus when a flow matches it automatically suppresses inbound actions.
I hope this helps!
If this was helpful, or correct, please be kind and mark the answer appropriately.
Michael Jones - Proud member of the GlideFast Consulting Team!
Michael D. Jones
Proud member of the GlideFast Consulting Team!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-11-2023 04:38 AM
Hello @Chandler2 ,
I'm also facing this same problem with one of my inbound actions, it shows in the logs that a record is created but actually it is not getting created. Have you found the solution for this problem?
Thanks,
Aditya Sharma
