Redwood Insights Premium and more observability updates for RunMyJobs: Elevating context and confidence

Article

As enterprise automation grows more distributed and more business-critical, visibility needs to keep pace. Workflows now span SAP landscapes, cloud platforms, legacy systems and third-party services. Execution data is abundant, but without context, it becomes harder to answer the questions that matter most: Where are risks emerging? What’s slowing us down? How does automation performance connect to business outcomes?

Redwood Software began addressing this challenge last year with the introduction of Redwood Insights, bringing observability directly into RunMyJobs by Redwood through standardized dashboards and operational analytics. That foundation gave teams clearer visibility into automation health and compliance without relying on disconnected tools.

RunMyJobs 2026.1 builds on that momentum with a broad set of observability-focused updates across the platform. This update expands how automation data is surfaced, shared and trusted, combining default insights, deeper analytics, tighter ecosystem integration and strengthened security. Together, these enhancements give teams a clearer context across their automation environments and greater confidence as automation becomes more central to daily operations.

Democratizing automation intelligence

At the center of RunMyJobs 2026.1 is Redwood Insights Premium, an expansion of the analytics and observability capabilities already available to RunMyJobs customers.

Redwood Insights Premium is designed for organizations that need deeper analysis and longer historical context as automation becomes more central to their operations. It extends observability beyond platform administrators to the business and domain teams that rely on automation outcomes.

Key capabilities include:

• A no-code dashboard designer that allows IT to create role-specific dashboards for different teams
• Extensive visibility into workflow health, execution patterns and emerging trends
• 15 months of historical data retention, expanding the existing analytics window for trend analysis, capacity planning and ROI conversations

IT teams can curate views for different teams and control access, while stakeholders gain self-service access to insights in their own context. This reduces reporting overhead and removes the “IT-as-translator” bottleneck without sacrificing consistency.

Unified transparency across SAP and the broader ecosystem

RunMyJobs has long supported integration across enterprise environments. In 2026.1, that integration extends more deeply into observability workflows.

For SAP-centric organizations, the out-of-the-box SAP Cloud ALM connector brings RunMyJobs execution data directly into SAP’s native Job and Automation Monitoring. Automation health becomes part of the same operational view SAP teams already use, improving coordination and reducing mean time to resolution (MTTR).

At the same time, RunMyJobs continues to integrate with leading observability platforms such as Splunk, Dynatrace, New Relic and AppDynamics. These integrations strengthen full-stack correlation, allowing teams to connect automation behavior with application and infrastructure performance using tools already in place.

Enhanced security and trusted AI, built in

In 2026.1, RunMyJobs’ security and governance foundations are further strengthened.

New capabilities include automated malicious file detection for all UI uploads with full audit logging, along with enterprise-grade moderation applied to all Redwood RangerAI interactions. These controls allow teams to benefit from AI-assisted troubleshooting and scripting while maintaining strict governance boundaries.

Support for Java 25 ensures the platform continues to align with the latest long-term support runtime for performance and security.

Modern deployment: Cloud Gateway

As automation environments become more distributed, reliable connectivity becomes essential. Observability and execution depend on consistent communication across cloud, hybrid and on-premises infrastructure.

The updated Cloud Gateway in RunMyJobs 2026.1 improves how the platform connects to these environments. It supports multiple active gateways at the same time, enabling higher throughput and load distribution across gateways. Intelligent routing allows traffic to be segmented by network or domain, while automated failover ensures continuity if a gateway becomes unavailable.

Together, these enhancements strengthen availability and performance across complex network topologies. Observability and execution data remain reliable even as infrastructure becomes more segmented and automation spans multiple environments.

Velocity through usability

Alongside these enhancements, RunMyJobs 2026.1 includes hundreds of usability and performance refinements. These changes focus on reducing friction in daily operations rather than introducing new workflows that teams need to learn.

Improvements across navigation, responsiveness and issue detection help users move faster and identify potential problems earlier. Routine interactions require fewer steps. Signals that once required manual investigation are surfaced more clearly within existing views.

Together, these updates extend RunMyJobs’ observability capabilities into a broader, more actionable intelligence layer. Automation becomes easier to understand, easier to manage and easier to optimize over time.

Already a Redwood customer? Review all the features released in 2026.1.

Ready to democratize your data? Request a demo of RunMyJobs, including Redwood Insights Premium, and see how tailored observability changes how your teams work.

Why clarity, not coverage, defines modern observability

Article

Imagine standing in a control room filled with screens. Every system reports green, and every dashboard is populated. The view feels complete. Then, a critical business process misses its deadline.

The data was there. The warning signs weren’t obvious. By the time the impact surfaced, the moment to intervene had already passed.

This is a familiar tension for many enterprise leaders. Visibility exists, but understanding doesn’t always follow. Monitoring tools confirm that systems are running, but they rarely explain how automation behaves under pressure and how delays ripple across dependencies or where risk is quietly accumulating.

The single pane of glass was an important step forward. It brought fragmented information into a shared view and reduced blind spots. What it doesn’t consistently provide is depth: the ability to move from status to meaning without manual interpretation.

That gap becomes clear the moment questions turn from “Is it running?” to “Can we rely on it?”

When insight depends on translation, risk increases

Most enterprises already collect enormous amounts of operational data. Automation platforms generate execution logs and performance metrics. And applications and infrastructure emit their own signals. So on paper, nothing is missing. But in practice, insight is scattered.

Understanding what’s happening across critical workflows often requires translation. IT teams pull data from multiple monitoring tools, correlate timelines and explain what technical behavior means for business outcomes. Leaders then depend on these explanations to assess risk, prioritize action and answer questions they know are coming.

This model is fragile. It slows decision-making and quietly extends mean time to resolution (MTTR), even when teams are working as fast as they can. By the time an issue is fully understood, the opportunity to intervene early has often passed, turning what could have been a minor disruption into a larger operational event.

Observability reduces that dependency. Correlating automation data and presenting it with context, it allows different audiences to access the insight they need without waiting for interpretation.

Why consolidation alone doesn’t create clarity

The promise of a single pane of glass is powerful when the goal is shared visibility into a specific domain — one platform, one set of processes, one operational context. It creates a common reference point and a shared understanding of what’s healthy and what’s not.

The challenge emerges when that same approach is stretched to cover the entire enterprise. A single view can only show so much. When automation spans applications, infrastructure, data pipelines and business services, compressing everything into one window often flattens the story instead of explaining it. 

Over time, this leads to dashboard fatigue, especially when green statuses can mask issues that matter deeply to specific teams. Different roles need different windows into the landscape:

• Process owners need to understand whether end-to-end workflows will complete on time 
• SAP teams need to see how automation execution affects business services and applications
• Platform teams need to connect workflow behavior to application performance and infrastructure health

Effective observability builds on the single-pane-of-glass approach with more of a panoramic view, where multiple, connected panes together reveal the full landscape. Each pane provides the right context for the person looking through it, while still drawing from the same underlying source of truth.

Context changes how problems are handled

Monitoring answers a narrow question: did something happen?

Observability answers a more useful one: why did it happen?

With cross-domain, correlated, up-to-date data, teams can see how workflows behave as part of the enterprise ecosystem, how dependencies influence response times and where delays originate — insight that directly shortens MTTR by narrowing focus to the point of failure instead of the symptom. 

The real impact shows up in consistency. Fewer surprises reach leadership. More importantly, service-level agreements (SLAs) stop feeling like commitments you hope to meet and start becoming outcomes you can actively manage. Ultimately, the organization spends less energy reacting and more time improving how critical processes perform.

So, the control room still exists, but it stops being a wall of indicators. It becomes a place where cause and effect are visible.

Resilience requires a longer memory

Operational resilience isn’t built in a single incident. It’s built over cycles.

Short-term monitoring captures what happened today, while observability preserves history and makes it actionable. With extended data retention, leadership teams can look across quarters instead of weeks. They can compare peak-period performance year over year, identify recurring bottlenecks and understand how changes in architecture or volume affect outcomes.

This longer view supports better planning and more credible conversations with the board. It also simplifies governance and audit preparation. Instead of assembling evidence manually, you can rely on a consistent execution history that reflects how systems actually operate.

A 15-month narrative, rather than the two- or three-month one many teams work with today, creates continuity. It allows leaders to explain not only what changed, but why it changed — and how those decisions improved reliability, protected SLAs during peak periods and strengthened the return on automation investments in the long run.

A more sustainable role for IT

When observability is done well, something subtle but important changes inside the organization.

IT teams stop being the place everyone goes for explanations. They’re no longer stuck translating technical signals into business impact after the fact. Instead, they set the conditions for shared understanding. The right information is available earlier, in context and in language that different teams can actually use.

That shift frees technical managers to focus on improving how systems perform rather than defending why something failed. It also changes how leaders engage. Conversations become less about status and more about trade-offs, priorities and what to improve next. Visibility no longer depends on deep technical detail or last-minute briefings.

This is why observability can’t be reduced to “better dashboards.” The real value is confidence: 

✅ Confidence that the systems carrying real business risk are understood

✅ Confidence that issues will surface early 

✅ Confidence that decisions are grounded in reality, not assumptions

Continue exploring observability

As automation continues to scale via Service Orchestration and Automation Platforms (SOAPs), the ability to understand, anticipate and explain performance becomes a strategic advantage. To learn more about how modern observability supports resilient, data-driven operations, explore Redwood’s approach to enterprise observability.

The automation talent shift: Building teams that thrive in the SOAP era

Article

After years of working with SAP customers, partners and internal teams, one thing has become clear to me: automation has outgrown its roots as a technical initiative tucked inside IT. Today, automation is the connective tissue of modern digital infrastructure and, increasingly, of the teams that run it.

What doesn’t get talked about enough is that this shift isn’t primarily about tools. It’s about us as humans.

That’s why I find the 2025 Gartner® Magic Quadrant™ for Service Orchestration and Automation Platforms (SOAPs) so relevant as both a technology lens and a talent and operating-model conversation.

SOAPs aren’t simply better schedulers. They orchestrate end-to-end business services with precision, context and intelligence. And when an organization adopts one, it doesn’t just modernize its automation stack, but reshapes how teams work together, learn and create value.

From my perspective, this isn’t a skills gap problem. It’s about how roles are naturally evolving. With the right guidance, encouragement and space to grow, people can thrive in change rather than just adapting to it.

The shift from task execution to service ownership

SOAPs dramatically expand the surface area that automation touches. We’ve moved from “run this job” to “run this entire business service — with events, conditions, dependencies and real consequences.” 

That evolution changes the nature of the work. You’re no longer optimizing isolated workflows inside a single system. You’re orchestrating processes that span ERP, SaaS applications, cloud platforms and external services. That requires broader thinking and deeper collaboration. The work itself becomes more strategic.

People are still central, but they’re now enabling resilience, business agility and real-time orchestration, not just maintaining automation.

What high-performing automation teams think differently about

The first real shift has to happen in how teams think about automation. Over time, I’ve seen successful teams move from:

• “Automate the task” → “Orchestrate the service”
• Siloed responsibility → Shared, cross-functional enablement
• Versioned scripts → Reusable templates and modular components
• Maintenance thinking → Platform thinking
• Support role → Strategic enabler
  

This mindset shift is subtle, but it changes everything from design decisions to how people collaborate across SAP and non-SAP landscapes.

How automation responsibilities are being redistributed

As SOAPs reshape operational models, new roles naturally emerge. Many organizations already have the talent; they just haven’t named or empowered these roles yet.

Some patterns I’m seeing more often:

• Process architect/Orchestration designer: Connects workflows across business services, APIs and cloud-based environments
• Automation data translator: Bridges operational logic with analytics, logs and business context
• Workflow monitoring and exception manager: Manages signals, dependencies and upstream/downstream impact
• Adoption lead or Change champion: Drives orchestration consistency across business ops, IT operations and development teams
• Automation culture steward: Shapes shared norms around reusable assets, platform thinking and feedback loops

Revisiting how automation work is distributed can unlock capacity you didn’t realize you had.

The conditions that make orchestration stick

Technology expands what’s possible. Culture determines what actually sticks. As automation spans more of the business, shared ownership becomes essential.

That starts with a shared vocabulary. If one team calls it “dependency mapping” and another says “event chaining,” you’ll end up with silos — not orchestration.

It continues with a learning loop that goes beyond training. People and teams need space to experiment, compare patterns and refine their instincts. As a leader, your job isn’t to prescribe every step but to create the conditions for repeatable learning that scales naturally.

And all of the above depend on clear ownership. Without visible leaders accountable for process optimization, templates and tooling standards, automation efforts remain reactive.

How to help your team thrive

If SOAPs unlock new levels of human potential, your team’s job is to take that and run. The environment you create — and the initiatives you choose to prioritize — will bring the shift to life.

At a minimum, I’d focus on the following.

1. Build capability with intention

Capability building can’t be accidental. It should be purposeful. Help teams build fluency in event-driven automation, API integration, cloud orchestration and monitoring patterns. Give legacy automation specialists room to evolve into orchestration designers or platform operators.

The goal isn’t to turn everyone into a developer. But everyone should understand how services fit together and how dependencies behave. You’ll be designing for resilience when your teams understand the “why” behind SOAP-driven workflows.

2. Create a structure that supports orchestration

Orchestration doesn’t thrive without structure. Establish an automation Center of Excellence as a guide for standard workflow patterns, exception handling and reuse. Make ownership explicit for templates, connectors and observability.

Most importantly, bring your practitioners into governance conversations. That’s how you remove friction between process design and automation design.

3. Equip teams with tools that let them excel

People do their best work when technology reduces complexity instead of adding to it. Choose platforms that make dependencies visible and support both low-code and advanced design approaches. Each persona should be able to contribute at their level.

I often ask one simple question: Will this tool make it easier for my team to design, understand and maintain end-to-end processes? If the answer is yes, the value shows up quickly.

4. Avoid the usual traps

Automation stalls when it’s treated as an IT-only scripting exercise, when adoption is an afterthought or when success is measured by output instead of outcomes. You can avoid these traps by formalizing enablement, designing for orchestration — not tasks — and tying KPIs to reliability and business impact.

Your people = your differentiator

SOAPs raise expectations for how work flows across the enterprise. But it’s your people who turn those expectations into outcomes.

When you make space for teams to think bigger about how data, work and ideas move across the business, you unlock something far more powerful than automation alone.

If you’re building that kind of culture, it helps to understand where the market is headed. The 2025 Gartner® Magic Quadrant™ for SOAPs report offers a grounded view of the Leaders and orchestration capabilities shaping the next chapter of enterprise automation — and the teams that will thrive in it.