Data & Analytics Product Documentation
Spaces
Apps
Templates
Create
EagleML and EJM
All content
Space settings
Content
Results will update as you type.
EagleML/EJM Basics
EagleML/EJM Installation
EagleML/EJM Configuration
EagleML Data Loads
EagleML Data Extracts
EagleML Data Maps and Examples
Instance to Instance (I2I) Feature
Manage EagleML API Client
EagleML/EJM Troubleshooting
Eagle Default Nuggetizer
Generic Load Enrichment
General EJM Triaging Scenarios
•
Tuning FTP/SFTP Timeouts for Downloading Files from FTP/SFTP
•
EagleML Validation Stream
•
Enable/Disable Message Center Streams with an RTR
•
Monitoring Stream - Stuck and Continuous
•
Enable/Disable Eagle Scheduled Events with an RTR
Workflow Waiting Queue
•
Workflow Waiting Queue Record Types
•
Workflow Waiting Queue - Possible Scenarios
•
Remove a File from the Workflow Waiting Queue (with Use Cases)
•
ORCH Tables and Their Structure
Incoming Files Processing Information
•
Stored Processing Information
Possible Incoming File Processing Scenarios
•
Incoming file has no corresponding workflow on the region
•
Incoming file that has a corresponding workflow on the region
•
Incoming file that has a corresponding workflow on the region being cancelled before processing
•
Incoming file that has a corresponding workflow and is a bundle trigger
•
Incoming file that has a corresponding profile
•
Incoming file that has a corresponding profile but processing gets canceled before results load
•
Pausing/Killing a Workflow or MC Stream
Known Issues
EagleML and EJM Best Practices (Restricted) WIP
EagleML/EJM Monthly Release Notes and Published XSDs
Data Rules Extensions: A Step-by-Step Guide
EagleML and EJM
/
/
Incoming Files Processing Information
/
Possible Incoming File Processing Scenarios
Summarize
Possible Incoming File Processing Scenarios
Dmitry Donosiyan (Unlicensed)
Kinga Huszno
Owned by
Dmitry Donosiyan (Unlicensed)
Last updated:
Nov 08, 2024
by
Kinga Huszno
1 min read
Loading data...
This section provides details on possible income file processing scenarios.
In this section
{"serverDuration": 35, "requestCorrelationId": "44f991ccfec74f85b3eb55a55715bd74"}