Workflow to consider: restarting expired job with input files

[Foxcapades]

Likely not relevant to most services, but service-multi-blast (mblast) has the case where the "input file" is a query that is persisted to the database. This allows mblast to revive expired jobs without needing any input from the user.

The platform itself should not and will not be responsible for the details of mblast's job revival method, however perhaps the platform should provide some methods around expired jobs that allow the revival of them provided handles on the inputs that were originally used when the job was started.

For example, in mblast's case, the service could call this hypothetical "revive" method and pass in an InputStream for the input file, allowing the platform to recreate the remote workspace and re-queue the job.

[Foxcapades]

In practice this is not needed, mblast can simply delete and recreate the job using the standard API calls.