Yes, this is normal at startup. No cache exists at first, so it's created.

The cache file contains the articles that the account has already posted so it doesn't repost them on the next fetch. So when you first start it up, obviously no cache file exists because no articles have been posted yet. After the cache is initialized, it should fetch articles and post them. It should start making a bunch of posts after it initializes but I can't remember if it may wait for the fetch interval. If nothing posted after, just stop it and start it again and it should go.

Okay so with setting up mine for the first time I notice now it does not initialize and post until AFTER the first interval rolls around... So after an hour it should start... I'm going to fix this so it runs on startup as well. But a work around if you wanna get it going is set the config to a minute, let it run to get populated, then change it back to an hour and start again.