Cache not expired if edit managed directly from content list

I'm using boost with gz enabled. I also use URL Aliases. I can access content by some methods the cache expires properly. If I edit using a slightly different method then the cache will not expire. Here's how I can edit without expiring:

administer->content management->content->(shows list of content)->edit link in content list

then make changes and save, drupal brings me back to the content list. The cache does NOT expire.

However, if I view the content by its url alias as a logged in user, then edit it, the cache expires correctly. This can be accomplished by either navigating directly to the page by url while logged in, then clicking the edit link, or by:

administer->content management->content->(shows list of content)->title link in content list, which uses the url alias, then edit on the node page

Not sure where the problem lies, but it seem like either node_api is not firing correctly or boost is unable to access the url alias once the hook is called.