cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Debugging a failure - limits on trace

0 Likes
902

Hi All,

I have a complex iFLow that reads the entire employee population (top of stack).

It runs for about 40 mins and fails with this:

<Exception> A sequence of more than one item is not allowed as the first argument of fn:concat() (<preferredName>, <preferredName>) </Exception>

Obviously this is a data issue, but I am having trouble debugging. The error does not give me the bad data.

Questions:

Is there a way for me to get the bad data?

If I turn on trace, it remains active for only 10 mins. This iFlow runs for 40 mins. Is there a way for trace to be active for longer than 10 mins?

Any and all help is deeply appreciated.

Regards,

-Anurag

Accepted Solutions (0)

Answers (3)

Answers (3)

manoj_khavatkopp
Active Contributor
0 Likes

Hi Anurag ,

Just to debug purpose try to add Write data store before the step where error is occurring , later which you can download the payload from datastore and delete the datastore step from your flow .

Make sure to set Transaction Handling to Not Required for debugging purpose so that data is stored even in case of error .

Thanks,

Manoj

0 Likes

Thanks Manoj.

I am not familiar with the data store.

How do I determine my Data Store Name. I don't seem to have any data stores.

manoj_khavatkopp
Active Contributor
0 Likes

Hi Anurag ,

You need to use "Write" data store step in your flow just before the step where your flow is failing. You can create a data store with any name . Check this link for more detail.

Thanks,

Manoj

0 Likes

Hi Priyanka,

I already have a groovy script to log payload, but my log is full, and no logs are displayed in "INFO".

So, I can change it to TRACE, but it has a limit of 10 mins.

PriyankaChak
SAP Champion
SAP Champion
0 Likes

Hi Anurag,

You can add groovy script to log payload.

Regards,

Priyanka