What does Workato consulting from AceMQ cover?
Recipe design and error handling, on-prem agent groups and their network path, custom connectors built with the Connector SDK, API Platform collections and clients, and promotion between Development, Test and Production. Every engagement starts with a written review and ends with a runbook your team keeps. It is a new AceMQ service line, delivered by AceMQ engineers with partner subject-matter experts.
How should Workato recipes handle errors and retries?
Workato's Handle errors step works like try and catch: the Monitor block holds the actions to watch and the On error block holds the fallback. Retries are off by default, can be set to at most three with a wait of one to ten seconds, and can be made conditional with Retry IF. In an API recipe, a request timeout ends the job without running the On error steps (docs.workato.com, read 20 November 2026). We apply one pattern across recipes and alert on the stable error_type_id, not on the unprocessed inner message.
How do we make the Workato on-prem agent highly available?
Put several agents in one on-prem group: Workato recommends it for availability, fault tolerance and load balancing, and a group spreads work across its agents. The agent makes outbound connections to Workato over TCP 443 and needs no inbound firewall ports, but a TLS-inspecting proxy can break its mutual TLS trust chain (docs.workato.com, read 20 November 2026). We check the group layout and the network path.
Do you build custom Workato connectors?
Yes. The Connector SDK builds connectors for apps Workato has no pre-built connector for, and the SDK gem lets engineers develop and test locally in their own IDE. Custom connectors are private by default and can be shared as open or closed source (docs.workato.com, read 20 November 2026).
How do we promote Workato recipes from Development to Production?
With Environments enabled, projects and their assets are deployed from the Development environment to Test or Production, and a collaborator needs the deployment privilege in both Development and the target environment (docs.workato.com, read 20 November 2026). We set up the project structure, connection and property handling, and a deployment routine that does not depend on one person.
Can we work with AceMQ on Workato without a long contract?
Yes. AceMQ works on Workato in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual contract that covers 24/7 support and proactive reviews. Many teams start ad hoc and move to an annual contract once the first engagement is done.
How much does AceMQ Workato support or consulting cost?
Every AceMQ proposal is tailored to your requirements: your Workato environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how Workato is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.