Overview
Reprocess configuration lets you define the endpoint to which a failed transaction stage can resubmit its message. When a message from a downstream system is invalid or has data problems, functional support teams can correct and resubmit it directly from Business Activity Monitoring (BAM) without waiting for the source system to resend.
Reprocessing is available only in the Custom Logging type of Business Activity Monitoring.
Business value
Reprocessing eliminates the round-trip communication between integration and source system support teams that would otherwise be required to recover from message failures. For real-time, mission-critical integrations, this reduces recovery time and keeps operations moving without external dependencies.
BAM tracks the count of reprocessed transaction instances, giving you an audit trail of all resubmission activity.
Prerequisites
Required permissions
| Action | Required permission |
|---|---|
| Configure a reprocess endpoint on a stage | Manage transactions |
| Perform bulk reprocessing and dynamic reprocessing | Reprocessing |
| Edit the message payload before reprocessing | Manage payload |
The Manage transactions permission is also granted to users with the Account owner, Contributor, or Reader role.
How it works
Reprocess configuration is set per stage within a Custom Logging transaction. You right-click the stage in the transaction flow editor and select Configure reprocess, then select an endpoint type and provide the connection details.
BAM supports the following reprocess endpoint types:
- HTTP Web Endpoint
- Azure Service Bus Queue
- Azure Service Bus Topic
- Azure Event Grid
- SFTP Endpoint
- Azure Blob Storage
When a support team member reprocesses a failed transaction instance from the BAM tracking view, BAM resubmits the message to the configured endpoint for that stage. Users with the Manage payload permission can edit the message body before resubmission.
BAM automatically masks sensitive values — such as Service Bus connection strings, HTTP URIs, and Event Grid topic endpoints — in the tracking view. HTTP headers marked as Sensitive are additionally masked and cannot be deleted or updated by the reprocessing user.
Steps
Use the following steps to configure, update, or remove reprocess settings for a stage. Navigate to the relevant business process in Business Activity Monitoring > Business Processes, then open the transaction containing the target stage.
Configure a reprocess endpoint
Configuring a reprocess endpoint on a stage enables support teams to resubmit failed messages from that stage directly within BAM.
- Go to the Transactions section in the business process.
- Click Edit transaction flow on the relevant transaction.
- Right-click the target stage and select Configure reprocess.
- Select an endpoint type from the dropdown.
- Enter the required connection details for the selected endpoint (see Configuration below).
- Click Update to save the reprocess configuration.
Remove a reprocess endpoint
Removing the reprocess configuration from a stage disables reprocessing for that stage.
- Open Configure reprocess for the stage.
- Click Reset to remove the current reprocess configuration.
Configuration
HTTP Endpoint
Enter the URI and select the HTTP method (PUT or POST). You can add or remove headers as needed.
Authorization — select one of the following methods:
| Method | Details |
|---|---|
| Basic auth | Enter a username and password. BAM encrypts the credentials and includes the Authorization header in requests. |
| Bearer token | Enter the API's Bearer token. BAM adds the Authorization header automatically. |
| API Key | Specify the API key name and value. BAM includes the Authorization header in requests. |
| OAuth | Provide the token endpoint URL and method (GET or POST). In the Body section, enter the request body. In Headers, specify the API key and value. In Query Parameters, add any query parameters to include in the target URL. In the Response section, set the response type (plain text, JSON, or XML). For JSON and XML, a JSON expression or XPath query is required to extract the token. The Token prefix field is optional for plain text responses. |
:::(Info)(Note:)
For the OAuth authorization method, Body, Headers, and Query parameters are optional inputs.
:::
Azure Service Bus Queue
Enter the Service Bus Connection string and Queue name. You can also specify User Properties and System Properties.
Azure Service Bus Topic
Enter the Service Bus Connection string and Topic name. You can also specify User Properties and System Properties.
Azure Event Grid
Enter the Topic endpoint, Topic key, Subject, and Data version. Specify the event type if required.
SFTP Endpoint
Enter the Host (server IP or domain name), Port number (SSH port), file Path, User name, and Password.
Azure Blob Storage
Select the Container name from the list of existing containers, or select Create New to create a new container. Specify a Blob prefix if needed.
Permission behavior
| Permission | What it allows |
|---|---|
| Reprocessing | Perform bulk reprocessing and dynamic reprocessing from the transaction instance view. |
| Manage payload | Edit the message payload before reprocessing. Users without this permission can reprocess but cannot modify the message body. |
Users who can reprocess cannot see the connection details of the configured endpoint — only the endpoint type is visible. Sensitive HTTP headers are masked for all users regardless of permission level.
Example scenario
An integration team runs a logistics platform where order messages are sent to an Azure Service Bus queue and processed by a Logic App. Occasionally, messages arrive with an invalid destination field that causes the downstream processing stage to fail.
The Notify Logistics Team stage is configured with an Azure Service Bus Queue reprocess endpoint pointing to a correction queue. When a failure occurs, a support engineer opens the transaction instance in BAM, reviews the tracked stage properties, corrects the destination field in the message body, and resubmits it to the correction queue — all without involving the source system team. BAM records the reprocess count in the environment dashboard.
Limitations
- Reprocessing is only available for Custom Logging type transactions. Data Queries transactions do not support reprocess configuration.
- Sensitive HTTP headers cannot be deleted or updated by the user performing the reprocessing.
- The URI (HTTP endpoint), Service Bus connection string (Queue and Topic endpoints), and Topic endpoint (Event Grid) are masked in the tracking view for all users.
Troubleshooting
-
The Configure reprocess option is not visible when right-clicking a stage.
Cause: The transaction type may be Data Queries, which does not support reprocessing. Alternatively, you may not have the Manage transactions permission.
Fix: Confirm the business process type is Custom Logging and that your account has the Manage transactions permission. -
Reprocessing fails with an authentication error on an HTTP endpoint.
Cause: The authorization credentials may be incorrect, expired, or not matching the expected format for the selected auth method.
Fix: Review the authorization settings in Configure reprocess. For OAuth, verify the token endpoint URL and response extraction expression are correct. -
The reprocessed message is not appearing at the target endpoint.
Cause: The connection string, queue name, topic name, or endpoint URI may be incorrect.
Fix: Verify the endpoint details against the actual Azure resource. For Service Bus, confirm the connection string has Send permissions on the target queue or topic. -
Sensitive headers are visible to a reprocessing user.
Cause: The Sensitive flag may not have been enabled on the header when the reprocess configuration was saved.
Fix: Open Configure reprocess for the stage, locate the relevant header, and mark it as Sensitive. Save and confirm the value is masked in the reprocessing view. -
Reprocess count is not incrementing after a successful resubmission.
Cause: The BAM environment dashboard updates the reprocess count after a processing cycle completes.
Fix: Wait for the next monitoring cycle and refresh the dashboard. If the count still does not update, check whether the resubmission reached the target endpoint successfully.