IntegrationHUB ETL Logs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2025 11:12 AM
Hi Listers,
Can someone please direct me to the tables where all IntegrationHUB transformations and resultant payloads are logged apart from the system logs - if such tables exist. I need to debug some strange behavior that happened few almost 6 days ago and I am unable to retrieve any related information from the system log.
Thanks & regards,
Victor.
- Labels:
-
Data Acquisition
-
Data Health Tools
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2025 07:46 AM
Hi @victor21 ,
As per my understanding IntegrationHub (IH) logs and payloads aren’t logged by default in a single dedicated table outside of system logs, but there are several useful tables where you can look, depending on what exactly you’re debugging:
1. Action Executions & Steps
These track every Flow/Action execution and each step’s input/output, which is very useful for debugging:
* sys_flow_context – Flow context (each execution of a Flow)
* sys_flow_execution – Flow execution details
* sys_flow_log – Execution log for Flows & Actions
* sys_hub_action_execution – Records each execution of an IntegrationHub action
* sys_hub_action_step – Records each step’s execution inside an action
These will show the actual payload, step inputs/outputs and execution results.
2. Spokes & Subflows
* sys_flow_subflow_execution – Executions of Subflows
* sys_flow_variable – Captures variable values during executions
3. MID Server Logs (for outbound calls)
If your IntegrationHub action uses a MID Server, you might also find related logs in:
* ecc_queue – Input/output payloads sent/received via MID server
4. Additional places to check
* syslog_transaction – End-to-end logs grouped by transaction
* syslog – General application logs (though limited retention)
* sys_rest_message / sys_rest_message_fn – Definitions of REST messages, but these do not store runtime payloads
Best practice tip as per my Understanding :-
If you need detailed payloads going forward, you could:
* Add a Log step in the Flow to explicitly capture payloads
* Write them to a custom table for auditing/debugging
* Enable “Log Payload” option in IntegrationHub Action (if you’re on Quebec+)
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025