How do you handle debugging when a workflow spans that many systems? Most workflow platforms, especially low-code/no-code, become painful to debug at scale.
Debugging at scale is simplified architecturally by separating the integration/glue from the core process logic, where the platform handles that integration glue for you. This decision focuses all the debugging efforts on a single Common Operating Script (as code), which decouples your high-level busines flow from the underlying integrations and infrastructure.
We also provide native distributed tracing (OpenTelemetry) across the entire distributed stack, with hooks to let you trace individual functions. This allows you to follow a single transaction through the Connector Hub and the Common Operating Script, correlating errors and tracking performance, across the various layers without manual log stitching.
Out of the box, we also include a centralized APM suite with Prometheus & Grafana (amp, and amq) with real-time app and infra metrics, and CloudWatch Logging attached to all the services, for centralized logs, to make this even easier.
