Comment 1 for bug 1644758

The logs aren't turning up anything of any particular interest. What might help is to see the full request and response from the cronjob, including HTTP headers. It *smells* like a caching issue, although it's interesting that the observed revision flip-flopped between the latest revision on the candidate channel and that on the stable channel.

I did notice a metadata request (snap refresh) that showed a delta download available on the candidate channel for the core snap (the same request also asked for updates to test-snapd-tools in the edge channel, but no delta was available) that corresponds to line 742 of https://travis-ci.org/snapcore/spread-cron/builds/178708453, but the client didn't request deltas so that shouldn't make any difference.