SyteLine and Mongoose Event System Troubleshooting Checklist
The Mongoose application event system in SyteLine 9 and CSI 10 runs handlers when framework or custom events fire. This checklist finds why a handler does not fire, fires twice, or leaves the user waiting.
0 of 25 items complete
6 critical items still open - these are the highest-risk gaps.
Definition
Execution mode
Runtime
Actions
Testing
Most event problems come from three places: the wrong event name (On versus Post), handler sequence against Infor-shipped handlers, and asynchronous or suspended handlers with no service to run them. Check those critical items before rewriting any action.
Send us a failing event
Share the Event Handler Status message and handler settings and we will suggest the most likely cause for your release.
Optional. The tool and every export work without this. No spam.
How to use it
Pick one failing event and one test record. Walk Definition first, because most handlers that never fire are attached to the wrong event or filtered to the wrong IDO. Then check Execution mode and Runtime, which explain handlers that hang or run late. Leave Actions for last: rewriting actions before you know the handler actually runs wastes the most time. Export the ticked list with screenshots of Event Status for the ticket.
Where this lives in Mongoose
Events, handlers and actions are maintained on the Events and Event Handlers forms. Framework events such as IdoOnItemInsert, IdoPostItemUpdate, SessionOnLogin, TaskPostPerform and BodOnReceive are built in; you add handlers to them but cannot add your own triggers for framework events. Run results appear on Event Status and Event Handler Status. Asynchronous and suspended handlers are processed from the event queue by the framework event service on the server.
- On events: before the change, can stop it
- Post events: after the change has happened
- Event Status: per event instance, Any Handlers Failed
- Event Handler Status: result, Times Failed, variables
Worked example
A handler meant to email purchasing when a PO line is inserted sends two emails. Event Status shows two instances. The handler was attached to both IdoOnItemInsert and IdoPostItemInsert during testing and both stayed active. Removing the On handler fixes the duplicate. Another handler never fires in production: its condition reads an event global constant that holds the test site code, so the condition is false for every production record.
Version differences and gotchas
Flag labels and tab names can differ slightly between SyteLine 9 and CSI 10 builds, so confirm them in your release help. Suspension runs synchronous handlers once in a validating pass that rolls back, then queues the commit, which surprises developers who log side effects in the first pass. Ignore Failure hides failures from the user but not from Event Handler Status. Infor updates can add shipped handlers to the same events you use.
Frequently Asked Questions
What is Infor Mongoose?
Mongoose is the application framework under SyteLine and CSI. It supplies IDOs, WinStudio forms, the application event system, TaskMan background processing and the IDO request service. The event system lets administrators react to framework events such as IDO inserts, logins, tasks and inbound BODs with handlers and actions, mostly without compiled code.
What is the difference between IdoOnItemInsert and IdoPostItemInsert?
IdoOnItemInsert fires while an IDO item is being inserted, so a handler can validate and stop the insert with a Fail action. IdoPostItemInsert fires after the item has been inserted, which suits notifications and follow-on updates. Attaching the same handler to both causes duplicate processing.
Why does my asynchronous event handler never run?
Asynchronous and suspended handlers are queued and processed by the framework event service. If that service is stopped or not configured for the database, handlers wait indefinitely. Check the service on the server, then Event Status for the instance state, then the handler's condition and global constants.
Where is the Infor Mongoose user guide?
Infor publishes Mongoose and SyteLine help on docs.infor.com, including the application event system guide covering events, handlers, actions, synchronicity, transactions, suspension and retrying. Use the help for your exact release, because form labels and supported features differ between SyteLine 9, CSI 10 and later Mongoose versions.
If you want an assistant on your own servers that explains which handlers run on an event and why one failed, we can build that over your SyteLine metadata.
Related Tools
SyteLine Mongoose Customization Deployment Checklist
Dev to test to production promotion checks for Mongoose forms, IDO metadata, extension class assemblies, SQL objects, events and reports on SyteLine 9 and CSI 10.
Infor SyteLineSyteLine TaskMan Background Task Troubleshooting Checklist
Step-by-step checks for background reports and utilities that sit in the queue, fail, or produce no output in SyteLine 9 and CSI 10 on-prem.
Infor SyteLineSyteLine ION BOD Integration Go-Live Checklist
Setup, scope, testing, cutover and hypercare checks for BOD based integrations between SyteLine or CSI 10 on-prem and Infor ION.
Developer ToolsSyteLine IDO API Security Hardening Checklist
Accounts, transport, tokens, request hygiene and monitoring checks for exposing the SyteLine IDO request service (REST and SOAP) to integrations and scripts.
More Developer Tools tools
See all- SyteLine IDO REST Request Generator
- SyteLine SQL Query Generator for Item, Job and Order Tables
- SyteLine SQL Blocking and Long Running Query Script Generator
- SyteLine Custom Table CREATE Script Generator
- SyteLine Mongoose Framework Events Reference
- SyteLine Event Action Types Reference
- SyteLine Event Action Parameter Functions Reference
- SyteLine WinStudio Standard Form Events Reference
- SyteLine Mongoose API Options Reference
Keep exploring
Free tools
- SyteLine Event Action Types ReferenceThe 26 action types on the SyteLine Event Actions form, with what each does, the parameters that matter and which ones make a handler wait.
- SyteLine Event Action Parameter Functions ReferenceThe expression functions you use in SyteLine event action parameters, with exact syntax, return type and the events where each one works.
- SyteLine TaskMan Background Task Troubleshooting ChecklistStep-by-step checks for background reports and utilities that sit in the queue, fail, or produce no output in SyteLine 9 and CSI 10 on-prem.
ERP fixes and how-tos
- How the SyteLine Event System Works for Workflow NotificationsHow SyteLine's Event Manager triggers email alerts, Mongoose scripts and ION Workflow off IDO methods: setup steps, Before/After timing, and troubleshooting.
- How to Send SyteLine Business Event Alerts to Infor Ming.leHow to turn SyteLine business events into Infor Ming.le alerts and notifications: event handlers, ION, recipients, noise control and a decision guide.
- SyteLine error -30006: how to find the real causeHow to find the real cause behind SyteLine error -30006 and other numbered messages: details dialog, message logs, server logs and SQL, in a repeatable order.
Guides
- SyteLine Event System Customization GuideCustomize SyteLine with the event system. Build event handlers, manage triggers, and extend CloudSuite Industrial without modifying base code.
- How to Configure Event Handlers in SyteLineStep-by-step guide to configuring event handlers in Infor SyteLine for automated responses to data changes, user actions, and system events across your ERP environment.
- SyteLine Event System: Automating ERP Workflows the Supported WayAutomate workflows with the SyteLine event system: event definitions, handlers, actions, approval routing, and how to troubleshoot stuck events explained.