What are Suspended Instances in Microsoft BizTalk Server?
Get alerts and manage suspended instances in BizTalk, grouped by application name, with Nodinite's intuitive monitoring and self-service features.
✅ Empower yourself with Nodinite – You don't need to be a BizTalk Server Administrator to resolve issues with suspended instances. Nodinite makes it easy and secure.
✅ Avoid the blame game – All sensitive operations are recorded in the Audit Log.
✅ Solve problems swiftly – Nodinite features Remote Actions to help you manage suspended instances efficiently.
✅ Statistics help you improve – Nodinite provides built-in reports to help you optimize your business with actionable insights.
As a BizTalk professional, you must proactively manage suspended instances. These instances result from operational errors or exceptions, and if you neglect them, you risk losing business transactions and impacting performance.
There are two types of suspended instances:
- Suspended instance(s) (resumable)
- Suspended instance(s) (not resumable)
Suspended instances for the selected BizTalk Server Application.
Warning
If you do not address your suspended instances, you will experience bad performance and may eventually run out of disk space. Business transaction flows will be interrupted, which is likely bad for your business.
Important
Suspended messages may include sensitive content. Any BizTalk Server Administrator can read (and potentially share) this information without traces when using the BizTalk Server MMC. With Nodinite, you can separate access using Role-based security. For your protection, all sensitive operations are log-audited.
1. Suspended instance(s) (resumable)
The run-time creates an instance whenever BizTalk Server initiates a process (e.g., receive, orchestrate, send). During processing, this instance can have different states, such as:
- Active Instance(s) – Still running and performing work
- Dehydrated Orchestration Instance(s)
- Ready to run Instance(s)
- Retrying Instance(s)
- Scheduled Instance(s)
These instances cannot be resumed, and the only option after an error is to terminate the instance (hence the name 'not resumable').
2. Suspended instance(s) (not resumable)
Each instance contains the actual payload (messages) and context properties. Whenever there is an error or exception, you may resume (or terminate) the instance. Resuming creates a new active instance, and the old one is automatically terminated.
Managing suspended instances
With the Nodinite BizTalk Server Monitoring Agent, suspended instances are grouped by BizTalk application name as Resources. They are organized into the following two Categories:
If your Monitor View allows the Remote Actions feature, you can perform the following operations to manage suspended instances (options differ for resumable and not resumable):
| Suspended instance(s) (resumable) | Suspended instance(s) (not resumable) |
|---|---|
| Manage (One, Selected, All) | Manage (One, Selected, All) |
| Terminate all | Terminate all |
| Details | Details |
| Edit | Edit |
- Suppress (one, selected, all)
- Unsuppress (one, selected, all)
- Terminate (one, selected, all)
- Resume (one, selected, all)
- Download (payload)
- Details
- Context Properties
- View suspended instance history
- Metrics
Next step
Spool count health check
Statistics for Suspended instances
Monitor Views
Configuration
Related
Suspended instance(s) (resumable)
Suspended instance(s) (not resumable)