Stream published to Akamai Universal channel throws unpublish out of nothing

Hello,

in our solution, we use AMS 5.01 for authentication and management of our input streams, which we sort into some playlist played on one output stream, which is then transrated (Wowza is usedfor this), then pulled back by AMS and published to Akamai, YT etc.

Everything is working fine, except one thing - after few minutes of publishing to Universal type of Akamai channel, some of the levels are unexpectedly dropped and disappear from the Akamai manifest files for HTTP streaming.

I first thought there is a problem on Akamai side, so I discussed this problem with their support - from their logs, it seems that our stream throws unpublish event at some point, so their logic discards it. There is nothing in our logic which could cause that and nothing in our logs about such behavior of the given stream.

For example, I push streams:

somename_500@1234567

somename_1000@1234567

somename_1500@1234567

and after 2-3 minutes, the first stream throws unpublish on Akamai side, the other two stays. I can see and monitor our outgoing streams in admin console and all seems fine and fluent.

I also tried some alternative scenarios of our streaming chain...

This is the full scenario which has the problem:

client side encoder->AMS->Wowza->AMS->Akamai EP

These scenarios does not have the problem:

client side encoder->Akamai EP

client side encoder->Wowza->Akamai EP

client side encoder->AMS->Wowza->Akamai EP

This one has the problem:

client side encoder->AMS->Akamai EP

From these, I assume, that chain works fine with AMS unless AMS is the component maintaining publishing to Akamai EP. Maybe there are some events/messages that AMS use during publishing which are not compatible?

Can You please advice, what can be behind such behavior?

Thank You

Roman