Marius van den Beek

Definitely has been updated many times since then. Let me know if there's anything to look at.

Moving the milestone to 25.1, if it is ready before the freeze (scheduled today) this can still make it.

> Can you please add tests for tagging the outputs of a regular tool and one for tagging the outputs of a map over job ? Can you please add...

Hey @lparsons, that is not possible unfortunately, url_for only works in a web context that is not available in the job and workflow handlers where these are used. The error...

In the meantime making an invocation's history shared might also be used to allow user access to the invocation (as a quick proxy ... it might still be worth sharing...

I'm gonna to the backend for the history access checks ... it is already there and we just need to flip the security checks from owned to accessible.

If you share a history that contains an invocation the invocation also becomes accessible now. What is missing is some hint that you might want to share the history if...

Thanks for checking, my test didn't actually use a user that wouldn't have access to the invocation 🤣. Should be fixed in https://github.com/galaxyproject/galaxy/pull/18746

> subworkflow ran without problems. I am sure there is a problem in your subworkflow, we don't produce this message unless there is a scheduling error. The error does mean...

@ahmedhamidawan you can download the workflow, it contains the subworkflow, or take the yaml workflow in https://github.com/galaxyproject/galaxy/pull/18731/commits/565911e85f1aa949ddd74ab873ccc75fbdd9f3ed and upload that to your dev instance.