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

Integration Suite Trace Level is not working

erlotayamen
Explorer
0 Kudos
2,377

After the most recent update, I've noticed there are strange behaviours coming from activating trace in IS, in particular, I can't seem to activate Trace level logs in the following iFlow. It remains as Log Level: Info for any runs that I do:

Screenshot 2024-12-15 at 22.32.52.png

even if the current configuration should be on Trace: 

Screenshot 2024-12-15 at 22.33.00.png

 I have tried to redeploy the iFlow, put the log level in debug, error and info then back to Trace.

 

Nothing changes.

 

Is anyone having the same issue? Any input or help would be appreciated!

 

Accepted Solutions (0)

Answers (3)

Answers (3)

MAVR
Product and Topic Expert
Product and Topic Expert

Hi @erlotayamen 

I have faced the same issue with or without extensions (cpi-helper); sometimes, it helps to undeploy and deploy, while others might not.

I have created a ticket for SAP support, but it might get more visibility if everyone who experiences the problem can create one. Something is definitely failing ( changing browsers is not the correct solution ).

Best regards,

Ricardo

 

Shubham_Kale
Newcomer
0 Kudos
Hi, did you get any solution after the ticket for SAP support?
WaltervD
Discoverer

Hi,

I faced the same Tracing-issue in Chrome and it worked again after Undeploy - Deploy , instead of just Restarting the IFlow. Maybe that helps!
( I also disabled CPI-Helper add-on, but I am not sure if that relates to this issue)

BR., Walter.

 

 

0 Kudos

Hello,

I confirm that the issue is not Browser related neither linked to CPI-Helper. In fact when using Cpi-helper to switch trace "on" we can confirm it has worked by checking the artifact status in "Manage Integration Content".

I agree with Walter, the procedure of undeploy (from Manage Integration Content page) then deploy from the iflow editor seems to do the trick.

I suppose it's indeed related to recent update and particularly the evolution of most used bricks like timer and groovy script (but this is only my personnal hypothesis).

tonynp
Explorer
0 Kudos

Hi 

I am also facing similar issue in Google chrome, Try to use in Edge it is working.