Hi @arpangarg sorry for the delay. Yes we have investigated the issue, and we have concluded that the wsk cli in its default form, doesn't create a cacheable path. Caching only works if the api endpoints are created using swagger. However, we have 2 solutions for you as we do think that your expecta...

Hi @arpangarg yes, the way it works now is that all requests that are sent to web actions are cached when using the `/api/v1/web/*`, and are not cached when using `/apis/*`. However we agree that this is not how it's supposed to be and we're going to add a fix by next week. I will update this thread...

Would it be possible to provide one of the executed URLs?The cache should activate in case the action is configured with 'Cache-Control': 'max-age=..` and the URL is exactly the same for consecutive requests. 

The problem is in the URL, it should be https://adobeioruntime.net/apis/89800-acswebpushapp-stage/acsutils/sendWebPushNotification . This would do the correct routing to the cluster that is active. There is a known issue with the `wsk api list` which might have given you this incorrect URL, we're wo...

All apis created with `wsk api create` should remain unchanged indefinitely. Could you please share the I/O Runtime namespace, and one of the endpoints that returned 404? I'll do an investigation on what exactly happened.