Troubleshooting

​

A service integration was skipped

If a service does not have a supported twin, Arga will flag the integration and skip it gracefully.

Check the list of supported twins and confirm that the service you are trying to use is currently available.

​

My sandbox behaves differently from production

Differences between sandbox runs and production data are often the signal Arga is designed to surface.

Review the run trace and the production comparison to understand where the workflow diverged. Differences can come from assumptions about how services behave or how users interact with them.

​

My tests already pass but workflows still fail

Traditional tests often validate narrow paths that developers explicitly define. Agents and real workflows may take unexpected paths across services.

Running the workflow inside an Arga sandbox allows you to observe behavior across integrations and identify issues that scripted tests do not cover.

​

A run triggered unexpected actions

Because Arga environments simulate real service behavior, agents may take actions that were not anticipated during development.

Use the recorded trace to inspect the sequence of events and determine how the workflow progressed across services.