Meta tags:
description=Two options in File Input Mapping — Processed tags and Query — are being deprecated. Existing configurations keep running unchanged. New configurations should use the alternatives below; we will contact affected projects before any breaking change.;

Headings (most frequently used words):

what, to, deprecating, processed, tags, and, query, in, file, input, mapping, changing, why, you, need, do, use, instead, faq, changelog, product, resources, about, follow, us,

Text of the page (most frequently used words):
the (17), file (16), tags (15), #processed (12), and (12), query (10), configurations (10), use (9), are (9), for (9), that (9), will (8), storage (7), projects (6), new (6), input (6), mapping (6), with (6), existing (6), not (5), you (5), this (5), created (5), run (5), branches (4), keep (4), affected (4), before (4), any (4), your (4), what (4), keboola (3), 2026 (3), twitter (3), contact (3), now (3), alternatives (3), can (3), using (3), should (3), transformations (3), files (3), breaking (3), change (3), csm (3), running (3), ids (3), incremental (3), processing (3), last (3), successful (3), linkedin (2), facebook (2), blog (2), jobs (2), customer (2), status (2), support (2), product (2), changelog (2), where (2), enabled (2), yes (2), anything (2), supported (2), path (2), may (2), same (2), still (2), sql (2), components (2), read (2), give (2), least (2), days (2), notice (2), work (2), job (2), filter (2), replacing (2), but (2), changing (2), next (2), reach (2), out (2), migration (2), both (2), options (2), branch (2), below (2), being (2), from (2), downloaded (2), deprecating (2), privacy, policy, terms, group, 2021, youtube, follow, about, github, sources, community, partners, webinars, stories, resources, developers, help, overview, rss, share, recommend, building, either, above, briefly, were, rolled, back, day, resuming, rollout, while, excluding, depend, see, further, disruption, related, only, does, affect, don, then, stop, working, faq, most, patterns, reduce, combined, cutoff, case, relies, specific, known, set, list, them, explicitly, configuration, needs, switch, own, aware, current, already, state, lives, mode, resets, reprocess, everything, problem, wait, plan, instead, success, manager, com, questions, filtering, longer, offers, nothing, right, need, incompatible, isolated, per, development, they, cannot, made, behave, consistently, across, production, cover, cases, have, additionally, been, superseded, adaptive, which, handles, platform, side, why, removed, api, json, payloads, accepted, today, used, going, forward, beforehand, free, form, metadata, field, inputs, option, tagged, each, after, consumed, could, exclude, via, practice, small, number, python, custom, doesn, unaffected, ignore, post, who, affects, two, deprecated, unchanged, try, tech, developer, portal, documentation,

Text of the page (random words):
deprecating processed tags and query in file input mapping product documentation developer portal status tech blog try keboola changelog may 27 2026 deprecating processed tags and query in file input mapping two options in file input mapping processed tags and query are being deprecated existing configurations keep running unchanged new configurations should use the alternatives below we will contact affected projects before any breaking change who this affects configurations using file input mapping in practice a small number of python transformations and custom components sql transformations and anything that doesn t read files from storage are unaffected and can ignore this post what s changing processed tags the option that tagged each file after a job consumed it e g downloaded so the next run could exclude it via a not downloaded filter query the free form metadata query field on file inputs both are being removed from the ui for new configurations existing api json payloads are still accepted today but should not be used going forward we will give at least 60 days notice before any breaking change and will work with affected projects 1 1 beforehand why both options are incompatible with storage branches isolated file storage per development branch they cannot be made to behave consistently across production and branch storage and the supported alternatives below cover the same use cases processed tags have additionally been superseded by created last successful run adaptive file input mapping which handles incremental file processing on the platform side what you need to do existing configurations using processed tags or query nothing right now your jobs keep running csm will contact you with a migration path new configurations use created last successful run for incremental file processing and tags file ids for filtering the ui no longer offers processed tags or query for new configurations questions reach out to your customer success manager or support keboola com what to use instead replacing processed tags created last successful run use this for any new configuration that needs incremental file processing for existing configurations you can switch on your own but be aware that the current what s already processed state lives in the file tags changing the mode resets it so the next run will reprocess everything if that s a problem wait for csm to reach out with a migration plan replacing query tags created and file ids most query patterns reduce to a tags filter combined with a created cutoff if your use case relies on a specific known set of files list them explicitly as file ids faq will my existing job stop working no existing configurations keep running we will give at least 60 days notice before any breaking change and csm will work with you 1 1 before then does this affect sql transformations or components that don t read files no only configurations that use file input mapping are affected is this related to storage branches yes on 20 may 2026 we briefly enabled storage branches on projects where processed tags were in use we rolled that back the same day for affected projects we are now resuming the rollout while excluding projects that still depend on processed tags so you should not see further disruption can i keep using processed tags or query on projects where storage branches are not enabled yes for now we do not recommend building anything new on either the alternatives above are the supported path share on twitter linkedin facebook changelog twitter rss product overview support help developers status resources customer stories webinars partners community github sources about contact us jobs blog follow us facebook twitter linkedin youtube keboola group 2021 2026 terms of use privacy policy