BusinessConnect (BC) audit log show outbound batches scheduled far in the future which never get triggered.
Article ID: KB0089121
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Description:
When examining the BusinessConnect audit log, X12 or EDIFACT outbound batches show up with scheduled transmission times that are far in the future. What causes this?
Symptoms:
See the description field.
Cause:
Batches with scheduled transmission date far in the future have been created in your environment by the Service protocol. These batches must be triggered by a back office BusinessWorks process using the Service protocol rather than the internal batching poller that BusinessConnect normally uses. The transmission time is set so far in the future to prevent the internal poller from triggering it..
When examining the BusinessConnect audit log, X12 or EDIFACT outbound batches show up with scheduled transmission times that are far in the future. What causes this?
Symptoms:
See the description field.
Cause:
Batches with scheduled transmission date far in the future have been created in your environment by the Service protocol. These batches must be triggered by a back office BusinessWorks process using the Service protocol rather than the internal batching poller that BusinessConnect normally uses. The transmission time is set so far in the future to prevent the internal poller from triggering it..
Issue/Introduction
BusinessConnect (BC) audit log show outbound batches scheduled far in the future which never get triggered.
Resolution
This is normal behavior.
Additional Information
Feedback
Yes
No
Powered by
