Gremlin and Azure Logic Apps

Test Azure Logic Apps reliability with Gremlin Failure Flags. Inject latency and errors into workflow actions to validate retries and error branches.

Azure Logic Apps makes integration accessible, which means workflows get built quickly by people who aren't thinking in terms of failure modes. A workflow can span half a dozen external systems within an afternoon, and each connector is a dependency with its own reliability characteristics.

The designer shows the happy path clearly and the failure paths not at all. Add Failure Flags to the custom function actions in your workflow and you can see the rest. With Gremlin, you can:

Find out which steps are safe to retry. Default retry policies apply whether or not they suit the operation. Injecting a failure shows you which actions duplicate work when they run twice.
Catch workflows that fail halfway. A run that stops partway may have already completed actions that can't be undone. Testing reveals what state gets left behind.
Check whether anyone is told. When a run fails silently, the business process it automated simply doesn't happen. Trigger a failure and watch whether an alert reaches a human.

For workflows quietly running business-critical processes, that last answer is usually the one worth having.

Building resilience on Logic Apps with Gremlin

Logic Apps is an application platform (or PaaS), which you can test using the Failure Flags sidecar and the experiments shown on the right. You can use Failure Flags to prepare your services for application-level failure modes on Logic Apps, such as:

High-latency function calls due to slow dependencies or high processing times
Validating error and exception handling logic
Experiments isolated to specific environments, customers, or any other application-level attributes

You can also run these expert-built workflows designed to replicate real-world failure modes on Logic Apps:

Dependencies: Failure Test

Simulate a failed dependency by dropping all network traffic to the dependency.

Try it

Dependencies: Latency Test

Recreate poor network conditions by delaying all network traffic to a dependency by 100ms.

Try it

Unreliable Networks - Dependencies

Simulate unreliable network conditions when communicating with dependencies by adding latency to API calls. Test whether your users are affected when dependency response times degrade.

Try it

* Failure Flags works wherever you can add the SDK to your application and run the Gremlin sidecar. Not every language and platform combination has been individually tested, and not all are officially supported. Check our compatibility documentation for what's verified, or get in touch if you don't see your runtime.

Learn more about Gremlin and Logic Apps

Intelligent Health Checks - Azure

Automatically monitor your Azure services during testing in one-click with Intelligent Health Checks.

Read

All product names, logos, and brands are property of their respective owners. AWS is a trademark of Amazon.com, Inc.; Azure is a trademark of Microsoft Corporation; Google Cloud is a trademark of Google LLC. Use of these names is for identification purposes only and does not imply endorsement or affiliation unless otherwise stated.

Avoid downtime. Use Gremlin to turn failure into resilience.

Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.

Get a demo

Gremlin and Azure Logic Apps

Test Azure Logic Apps reliability with Gremlin Failure Flags. Inject latency and errors into workflow actions to validate retries and error branches.

Why Logic Apps reliability is important

The designer shows the happy path clearly and the failure paths not at all. Add Failure Flags to the custom function actions in your workflow and you can see the rest. With Gremlin, you can:

Find out which steps are safe to retry. Default retry policies apply whether or not they suit the operation. Injecting a failure shows you which actions duplicate work when they run twice.
Catch workflows that fail halfway. A run that stops partway may have already completed actions that can't be undone. Testing reveals what state gets left behind.
Check whether anyone is told. When a run fails silently, the business process it automated simply doesn't happen. Trigger a failure and watch whether an alert reaches a human.

For workflows quietly running business-critical processes, that last answer is usually the one worth having.

Building resilience on Logic Apps with Gremlin

High-latency function calls due to slow dependencies or high processing times
Validating error and exception handling logic
Experiments isolated to specific environments, customers, or any other application-level attributes

You can also run these expert-built workflows designed to replicate real-world failure modes on Logic Apps:

resources

Learn more about Gremlin and Logic Apps

Avoid downtime. Use Gremlin to turn failure into resilience.

Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.

Get a demo