BizWeaver 2.13.10: Your Integrations Just Got Harder to Break

BizWeaver 2.13.10 gives you eyes on every connection and a guardrail against duplicate runs.

Most integration problems do not announce themselves. A SQL login expires. A REST endpoint starts timing out. An SMTP password rotates and nobody tells the system that moves your data. The workflow keeps firing, the errors pile up quietly, and you find out when a customer asks why their order never posted.

That gap between "something broke" and "someone noticed" is where trust in your integrations erodes. The latest BizWeaver release closes it.

See every connection at a glance

BizWeaver 2.13.10 adds Connection Health Monitoring to the Connection Manager. Every connection now carries a health status you can read in one look: Healthy, Degraded, Failed, Stale, or Unknown.

It covers the full range of what you actually run:

• SQL Server
• SAP HANA
• SAP Business One (DI API and DI Server)
• SAP Service Layer
• REST and HTTP
• GraphQL
• SMTP email

You get more than a pass or fail. Each connection tracks its response time, success rate, failure count, when it was last checked, when it was last used, and the most recent error message when a check fails. It also tells you whether a connection is actively in use or has gone dormant, so you can spot the integration nobody has touched in a month before it becomes a surprise.

Made a change to a connection string? Test it on demand and confirm it works before you walk away. And BizWeaver checks your connections on its own schedule in the background, so a failure gets caught whether or not anyone is watching the screen.

When a connection's health turns for the worse, BizWeaver emails your team automatically. Your people react before the workflow does, not after.

Stop the same workflow from running twice

The second problem this release solves is quieter but just as costly: the same workflow running twice at the same time.

A scheduled run overlaps with a manual one. An event trigger fires while the last batch is still processing. Two copies write the same records, double-post transactions, or trip over each other's data. Cleaning that up takes far longer than preventing it.

Smart Queuing prevents it. Turn it on for any workflow and BizWeaver checks whether that workflow is already running before it starts another copy. If one is in progress, the new request waits in a queue instead of running alongside it. The moment the first run finishes, the next one starts on its own. No manual intervention, no collisions.

It recognizes runs from every source, so a scheduled job will not collide with one you launched by hand or one kicked off through the API. A new Smart Queue view shows you exactly what is waiting. And because it is a simple per-workflow toggle, you apply it only where overlapping runs actually matter.

What else is in this release

Alongside the two headline features, 2.13.10 tightens a number of rough edges:

• Fixed Salesforce authentication failures from the Web Service tool.
• Restored the workflow execution log that was missing from the bottom of the window during test runs.
• Fixed health status alert emails that were not being delivered.
• Clearer descriptions of BizWeaver services in Settings, including a plain message where Basic Authentication is not supported for connection testing.
• The Test Connection button is now disabled while the Connection Manager is still loading, so an early click cannot cause trouble.
• Updated the SMTP email component to a newer library for better compatibility and stability.

A quiet upgrade with a loud payoff

The upgrade itself is straightforward. Database migrations ship with the release, so make sure they are applied when you move up. The Health Status column appears in the Connection Manager on its own after upgrade, with nothing to configure to start reading it. To receive health alert emails, confirm your BizWeaver notification settings are in place and health notifications are turned on. Don't worry, you'll only get an email when a connection becomes unhealthy. Smart Queuing stays off until you switch it on for the workflows that need it.

None of this changes how you build integrations. It changes how much you have to worry about them. You spend less time wondering whether your connections are alive and less time cleaning up after runs that never should have overlapped. Your integrations do what you set them up to do, and they tell you the moment they cannot.

If you run BizWeaver, talk to your Third Wave team about moving to 2.13.10. If you are still stitching your SAP Business One integrations together by hand, this is what running them with confidence looks like.