Hi, i noticed workflows are not using the cache, even though the option was selected in the query-settings.
Is caching for workflows not possible or just not implemented?
Thanks and best regards 
1 Like
Hi @flaschenpost-wha! Caching for workflow queries is currently not supported, nor is it on the immediate development roadmap. It's technically feasible just not currently prioritized - I'll bump the internal feature request on your behalf!
Is there a particular use case that you have in mind?
Hi @Darren, the use case is the exact same as some db- or REST-Query in some App/Module: don't want to hit the server too regulary, because the results from the workflow are allowed to have some delay and won't need to be live.
In my special case some API-Endpoint is used in a dashboard (which runs on mulitple stations), but we have to add some informations from other endpoints and process it with some python-code, so we decided on a workflow to make handling in the module much easier.
It would be a much better user-experience, if the not available options would be deactivated so it is clear, which functionality is usable and which isn't.
Technically the workflow gets some JSON-Input and provides some JSON-Output, so caching should be similar to the normal query-caching.
1 Like
Make sense! As mentioned above, I've updated our internal tracking of this feature request in order to reflect your interest and will keep you updated. We're actively doing Q4 planning, as well, so this is a good time for a bump!
Hi, very good initiative @flaschenpost-wha!
@Darren We would also need this to avoid loop queries to fetch the same details per iteration.
An example use case is triggering email sends and fetching translations from our database. If the workflow triggers hundreds of emails, it would fetch the same translations from the database on each iteration. It would be necessary to fetch those only once per language (the used language is defined in the loop iteration's value) and reuse them on later loop iterations specifying the same language.
If possible, it would be nice to have cache working in workflows like they do on Apps.
1 Like
Hi @eljass, we found a workaround today: Instead of using the "workflow"-Option in the Query we switched to REST-API-Call hitting the Workflows Webhook, using the X-Workflow-API-Key in the Headers and the Inputs in body as JSON.
This way the cache can be used on a workflow, as long as the workflow is only used in one query.
But: If you call the translation-API from the Email Workflow itself, it will still not solve the problem.
1 Like
Really appreciate you sharing an intended use case, @eljass!