> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Ansible Playbook task response fixed

> Breaking change notice that Gateway task connectivity failures now correctly produce an error state in Platform 6, rather than a success state.

In prior versions of Itential Platform, when `app-ag_manager` invoked an action in Gateway through a workflow task, the finish state of the task was always successful even if the request to Gateway failed. The `playbook` task was treated as a success, and the workflow continued along the success path despite a clear "No provider available for method" error message.

With Platform 6, Gateway tasks now treat Gateway connectivity problems as errors. When AGManager fails to connect to Gateway, the task enters an error state and the job progresses down the `error` transition path.

![](/_fern-img/bf5ef93501a996679e855d757915f34006afcfd91b0bc40ae935c860d856416f.webp)![](/_fern-img/05bb2b3e4722efec705e7bc9c551d3ce7ca4f12103dcea2fdbb2a7294aaaf410.webp)

When AGManager is able to connect to Gateway, the task returns a successful response as shown below.

![](/_fern-img/0804643c3bd6ea6d65b31d457b7ec81edfb25c56d067d21ed36de5376072d813.webp)

### What should I do?

Check the error handling logic downstream of any Gateway tasks in your workflows. If your workflow logic depends on those tasks taking the `success` path when the Gateway adapter is offline or the task could not otherwise be invoked by the platform, you must now handle those cases using an `error` transition type and the `error` task output instead.

If you need additional support or require more information, contact the [Product Support Team](https://itential.atlassian.net/servicedesk/customer/portals).