Seems the new deployment still using older resources, clear cached pages after re-deploy should fix it.