Overview
Almost everything Spek shows you is a cached read of the store, not a live call. That is what makes the app fast, and it means a value can be a little behind.
What is cached
Your listing text, your app catalog and your screenshots are stored after they are read. Keyword research is refreshed when you run the agent. Spek also refreshes store reads when you open a surface that needs them, and on its own schedule.
The app switcher shows the app's version and store status, and flags a connection that needs attention.
The changelog
Changelog in the sidebar is the history of what changed on your listing and when, market by market, including changes made outside Spek.
Rows the agent authored carry a marker, so you can tell your own edits from proposals you applied.
Common questions
A value looks out of date.
It is a cached read. Running the agent refreshes the research and the listing for the markets it covers.
First identify whether you are comparing the Spek draft, the synchronized provider record or the public store page. Those stages can differ legitimately. Include the exact field, locale and time of the external change if you need support to investigate a value that remains outdated.
Someone edited the listing in App Store Connect. Will Spek notice?
Yes. The next read picks it up, the changelog records it, and Ready for review asks which value to keep rather than overwriting it.
How can I tell a stale read from an unsaved draft?
Check the Editor's save state and whether you are looking at Draft or Live. A draft is your working copy in Spek; the synchronized provider value is the baseline read from the store. A Saved draft can legitimately differ from Live before publishing, while a provider read can be behind a change made elsewhere. Identify which stage you expect to have changed before troubleshooting. This avoids repeatedly editing a correct draft when the actual question is whether the latest provider state has been retrieved.
What should I check after editing directly in App Store Connect?
Confirm the app, locale, version and field you changed, then compare that record with Spek's synchronized view when it refreshes. If you also have a Spek draft, review the two values before publishing so the desired wording is clear. Changelog can help establish the sequence once the relevant store information is read. Do not assume a difference means data was lost: it can reflect separate working and provider copies, or the timing of the latest read.
Does refreshing store data start new keyword research?
Store records and research serve different purposes. Reading a current listing or account catalog should not be treated as proof that a fresh proposal pass ran for every market. Use the Agent's visible run state to understand research and proposal work, and use the relevant page's provider information to understand the listing baseline. If you need new suggestions, explicitly review the market scope for that request. Keeping the two activities separate makes it easier to explain why listing data and keyword observations have different timestamps.
What details help investigate data that still looks outdated?
Identify the exact app, market, field and view, then describe the value you expect and where you verified it. Include when the change was made and when you last checked Spek. A screenshot can help if it contains no private credentials or customer information. Comparing a public store page with an editable provider version can create an apparent mismatch, so say which one you used. That context lets support investigate the relevant read instead of guessing from a general report that the dashboard is out of date.