New automation trigger, **Low keyword stock**: when fewer than the given number of approved keywords remain in a research, a new keyword research starts on its own.
Blog posts can have templates too: set the recipe once (tone, knowledge source, model, images, cover, target menu), and every article — manual or automated — is written with it.
Changed
The blog step in automations is now as simple as the post step: it only asks for a template — brand, blog account and topic all come from it.
You now decide which menu item of your store your blog articles are filed under. Your blog account has a new field (**Hova kerüljenek a cikkek?** — where should the articles go?) listing your store's actual menu items: by default we offer the one where your existing articles live, marked **(javasolt)** (suggested), but you can pick any other. The article's **Publikálás** (Publish) step has a **Hol jelenjen meg?** (Where should it appear?) field too: you can see where the article will land, and you can override it for that one article — a seasonal menu, say — while the account's setting stays as it was. Until now the system worked your blog menu out on its own, which was right for most stores — but if you had no published articles yet, it had nothing to go on, and the article was left out of the store's blog listing. That can't happen any more. The detection got more accurate too: we suggest the menu item where **most** of your articles are, so one article forgotten in an old, abandoned menu can't skew the choice. (UNAS stores; Shoprenter has a single article list, where articles land in the right place by themselves.)
The automation editor's **Action** menu now only offers steps that actually make sense. Until now you could build a rule that quietly did something other than what you expected: a date set alongside immediate publishing never took effect, and topping up the keyword set next to a post only burned your credits. Those steps no longer appear where they don't fit; the ones blocked only by order (such as **Schedule it** without a date) stay visible, greyed out, with the missing piece spelled out underneath. You can still create several pieces of content in one run — you just set their type in one place. Nothing is removed from your existing automations: if one of them still contains a step that no longer takes effect, that row gets a yellow warning and you decide what to do with it. New: you can also delete the **Create…** step, so you can build an automation that only keeps your blog topic set stocked.
Fixed
Analytics no longer goes quiet when data is missing. It could happen that the Facebook view sat empty — no numbers, no posts, no warning — even though nothing was wrong with your account: it was enough for Facebook to retire a single metric, and that wiped out the statistics of every one of your Facebook posts, likes and comments included. From now on such a dropout only takes that one number with it and the rest of the data still arrives; and if an account's daily figures stall, we still fetch your posts' statistics. If something is missing anyway, we say so: the "stale account" bar now names the reason too (an expired connection, for example), and a separate, quieter notice tells you when the account's figures are fresh and only a few posts' statistics haven't arrived — the next daily refresh picks those up. A new help section explains what these bars mean. [Analitika: hogyan teljesítenek a posztok](/help/analitika)
**Generate from template** now actually starts. It could happen that the post was created, the editor "thought" for minutes, then said the generation never started — and it really hadn't: the work was meant to be kicked off by your browser in a separate request, which could get lost while the editor was opening, and then nothing happened on the server at all. From now on creating the post and starting the generation happen in a single step, and the work carries on server-side even if you close the tab. We also warn you in advance when a template's visual recipe won't produce an image: if the recipe would start from an existing picture (Logo, Animation or Resize, with no image generation), there is nothing to work on in a freshly created post. You see this in the template editor, in the template picker and in the campaign settings before you start it — you can still run the generation, the decision is yours. The same warning appears on a post's **Generálás** (Generate) button when the gallery is empty. [A sablonból csak szöveg készült, kép nem — miért?](/help/sablonbol-nem-lett-kep)
Your automation no longer skips a post in silence. It could happen that the automation wrote the text and created the image, yet the post never went out: it stayed a draft in the calendar, and the run log said "Error — No content was created" even though the content existed. The cause: while the text was being written, another background run started in parallel, saw the work as unfinished and closed it. From now on nothing else can touch a run in progress, and we only say that no content was created when that is actually true.
