New App Developer Endpoint: Retrieve Active Executions
A new API endpoint has been introduced for Eloqua app developers and integrators, allowing retrieval of all currently active executions for their apps. Previously, when an app experienced an outage or failure, there was no way for a developer to identify which executions (such as in-progress syncs, data pushes, or automated workflows) were left incomplete or stuck in the system. This limitation could result in inconsistent data states, lost records, or missed automations—especially problematic for mission-critical marketing integrations and system reliability.
With this new endpoint, app developers gain the ability to programmatically query the Eloqua platform for a list of all active or in-progress execution threads associated with their app. This provides crucial architectural visibility for recovery scenarios, as developers can now identify, resume, retry, or mark executions as errored based on current processing status. This change also lays the groundwork for more resilient and robust integrations between Eloqua and third-party systems.

Code Sample
- App developers will be able to retrieve active executions for the install instance using this new endpoint:
GET /api/cloud/1.0/apps/{id}/activeExecutions
- Authenticate using the install instance
- Query parameters:
- startDate (required)
- endDate
- serviceInstanceId (required)
- offset
- limit (default and max is 1000)
Business Benefits:
- Resilient Integrations: Minimizes data loss and disruption during outages by giving developers clear recovery options for stuck or in-progress operations.
- Operational Transparency: Enables teams to monitor, audit, and manage app performance and state transitions more effectively, supporting uptime and SLA commitments.
- Enhanced Troubleshooting: Provides actionable insights for support teams to resolve user issues faster and with greater accuracy, improving customer satisfaction.
- Reduced Manual Intervention: Streamlines post-outage recovery, reducing manual error tracing and corrective actions, and enabling more automated error handling logic.
Steps to Enable and Configure
You don't need to do anything to enable this feature.