Could you post the Test connection log once for both of your publishers (where it is fine and where it is not) ? 

The log which you have posted does not seem like an error, it looks just like a debug statement. And 403 probably just implies that the configured transport user or Agent User ID probably does not have enough permissions. I believe your transport user will also have to be available on the publish in...

Checking error logs would be the best bet right now. Otherwise if possible, please share the package via DM.

end would still be required for the set ACL block I believe. Without it the syntax would still be probably broken. So, it should be something like { "scripts": [ "create group \"Public-Offshore-Author\"", "set ACL for \"Public-Offshore-Author\"\n allow jcr:read on /content/mysite/en/Produ...

Are you seeing any errors in logs or console ? Is the container resourceType breaking at other places as well or just in your report builder ? And although it should not break the report builder but I see you are using coral2 datepicker, can you try updating it to coral3 i.e. granite/ui/components/c...

I think you should be able to use the date filter. Are there any challenges which you are facing ? Assuming you have a content fragment that has a field eventDate of type Calendar, you should be able to create a query to filter on that. Something like :query eventByDate($eventStartDate: Date) { ev...

https://sling.apache.org/documentation/bundles/content-distribution.html#events these events were not helpful ? 

Have you enabled the advanced networking as mentioned here https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/development-guidelines#sending-email Once that is done, you will have to update your Day CQ mail service as well, right now as per yo...

Just as an update for everyone this is a bug in recent cloud SDK versions. We raised a ticket for this internally and Adobe confirmed it. Their engineering advised the fix will be included in the next Cloud Foundation release that is planned to happen between 11 and 25th July.

Hi @LidermanGiraldoEscobar This is a bug in recent cloud SDK versions. We raised a ticket for this internally and Adobe confirmed it. Their engineering advised the fix will be included in the next Cloud Foundation release that is planned to happen between 11 and 25th July.