@Dukuo commented on @yuri’s file : I actually had this issue, but I re-deployed the api altogether because of another issue, then this logs thing dissapeared.