Can not Update my workflow
How does Editorial know that I previously shared workflow and offers me an update rather than a new link? I did ...
- upload RV: Workflow Installer, update it several times
- deleted it locally to test it as a fresh install
- installed again on the same device (no other changes made at all)
- and when I want to share updates it doesn't offer me Update, just Share
... don't want to create new link, new entry at editorial-workflows.com, just want to update my old one. How this is done internally? I mean, is there a way to fix this, to tell Editorial that it's my workflow?
Commands.edcmddoes not contain anything useful in this case as well, ... Any idea?
Discussion started with RV: Forums New Discussion workflow
Basically, a randomly generated "editing password" is stored on the device for each shared workflow, and it's associated with the workflow's unique identifier (UUID). When you install any workflow though (regardless of who created it), it gets a new, random UUID, so the association breaks...
Anyway, I just made this little workflow/script: → Restore Shared Workflow... — If you run this on the same device where you shared the workflow, it can re-install it in a way that also restores/preserves the editing permission.
You rock, as always! :-) Thanks, this did the trick and workflow is updated.
SharedWorkflows.sqlitebe included in
Editorial Backupas well?
@omz there's an issue with your Restore Shared Workflow. Actually it's an API issue, not workflow issue. The problem is ...
Recent Workflows Endpoint
When I get
workflow_datafrom recent workflows endpoint and store it directly to
.wkflvfile, workflow does work perfectly.
When I get
workflow_dataare crippled in response and it leads to ...
... and workflow installed in this way doesn't work at all. Just compare
$url?format=jsonand you'll see. They differ. Wrong one is Workflow Info endpoint.
This is the reason why I removed direct save of '.wkflv' files with
RV: Workflow Installer. I switched to
editorial://add-workflowscheme to be safe.
I see, thanks! I've just deployed a server-side change that should fix this issue.
Yep, confirmed, does work now. Thanks for the quick fix.
Awesome workflow! Thanks!