DSP Automate / Transform - Target Processing Issues with Automate

Answered

Joseph Flesche

• August 28, 2020 12:50

DSP Automate / Transform - Target Processing Issues

I have an Interface setup in Automate that contains the following.

1. Workflow to notify the start processing.
2. Reset Targets in case there were previous issues.
3. Process 3 targets (other Interfaces that I have contain different number of targets to process depending on what we are doing).
4. Workflow to notify the completed processing.

For various Interfaces, I keep getting targets (they seems to be the same ones) that keeps failing; ttILOA in the screenshot above. Every time we process this Object through the Interface, it fails at different source rules within the target. Today it has failed on step 15/113. When looking at the rule in error the errors states Error Thread was being aborted. TargetSourceRule: srILOA_DF_NewCoWave1_ILOA_zBEBERUpd d050620d-a557-438e-9eb7-f3a3763ea564 failed to execute.

When I look in Monitor for the JobID, it is showing as failed.

The rule that fails is always a standard update rule; FieldName to zFieldName. When I run the View then the associated Stored Procedure in SSMS, there are no errors / issues. If I continue the queue, the target finishes without any issues.

In looking at the Tasks / JobID, you can see that the rule in error works properly. In looking at the details of the target table, it appears that it did run on the previous, failed, queue running, hence the 0 second duration (there is a where clause of IS NULL on the field being updated).

When I run the target "manually" through Transform (by clicking on the Process button), the target processes without any issues.

The previous rule that had issues is now showing as run successfully.

In looking at the Interface history, it appears that Automate is showing that the Interface is still running (it is not, I already manually ran the last target) and thus out of sync with the processing.

I read through the documentation on Automate here. But I'm not too sure what I am doing wrong with the setup here. Any suggestions / input is welcome. A summary of my questions / concerns / issues...

• Why is target processing failing when running through an Automate Interface?
• Why does the Automate Interface still show as running?

0

• Best answer

  

  Stephen Audey

  • September 01, 2020 15:55

  Hi Joe,

   

  Please open a support ticket in the support portal (https://support.syniti.com/) and we can assist you investigate why this behavior may be occurring.You can copy the information you posted here and include these items:

  1. The results of this query in Excel with headers for our team to review:

  SELECT TOP 1000 [LogEntryID] ,[LogType] ,[ParentLogEntry] ,[PageID] ,[JobID] ,[TaskID] ,[Event] ,[StartTime] ,[EndTime] ,[Description] ,REPLACE(REPLACE(REPLACE(Comment, CHAR(10), ''), CHAR(13),' '),',','') AS Comment ,[OkToDelete] ,[Acknowledged] ,[ChangedOn] ,[ChangedBy] FROM [CranSoft].[dbo].[LogEntry] ORDER BY 1 DESC 

  2. How are you running the Automate job?  Are you clicking one of the buttons on the vertical of the Automate Job and if so which one?  Or is it running on a schedule?

   

  Best Regards,

  Steve Audey

  Syniti Support

  0

Please sign in to leave a comment.