Scenario: Replication set runs once weekly to provide data for subsequent processing by IPA for output file from Cloudsuite to Epic.
Background: I have created an IPA to process the replication set output data and format it to be consumed by Epic. I had created a service definition to attach to the replication set where the IPA would automatically kick off from the completion of the replication. However, I was recently advised to use job console in lieu of a service definition. I tried this method to review the differences by creating one job to 1) run the replication and another to 2) PFiTrigger start the IPA. Both jobs were placed in a job stream in the respective sequence.
However, I found that the replication set is taking an unusual amount of time to complete for the data being replicated; there's an error for the "UnlockReplicationSet" error and the Action Request is "Active with failed triggers". My concern is that I'm not sure how to troubleshoot this from an Async view, whereas with a service definition I can dig into errors from the IPA's workunit.
TL;DR -- I'm asking the community to make the argument for when, how and why you would choose to use a service definition over compiling actions in a job/job stream and conversely.
