Share a job
Sharing gives someone access to a job's configuration and all of its files. Use it to hand work to a colleague, or to give Rescale Support what they need to diagnose a problem.
Both input and output files become visible to the recipient, there's no partial share. Check what's attached before sharing a job outside your immediate team.
Share with a colleague
From the jobs list, click Share on the job's row, or open the job and use Share there.
- Enter the recipient's email.
- Optionally add a message.
- Confirm.
They get an email with a direct link. Once in, they can inspect the setup, SSH into a running job to watch it live, or download outputs from a finished one.
Sharing works for running and completed jobs. Sharing a running job is a good way to get a second opinion while there's still time to act on it.
This panel shares one job. To hand over a batch, put the jobs in a Workspace Folder and share the folder: everyone you share it with gets every job inside, and anything added later. That is the only way to share more than one workload in a single action.
If the recipient isn't a Rescale user yet
Sharing with an address that has no Rescale account fails with an error, and an invitation request goes automatically to your workspace and organization admins. Once the account exists, share again.
So a failed share isn't a dead end. It's started the process. You may want to tell your admin to expect it.
Revoke access
- Open the Jobs list.
- Click the Shared User icon in the job's Shared column.
- Click the X next to each user to remove.
- Click Apply.
Share a job with Rescale Support
This is how Support gets access to diagnose a problem job.
Rescale has no access to your jobs or files unless a job is explicitly shared. Support asking you to share a job isn't a formality: without it they genuinely can't look.
- Open the sharing interface as above.
- Select the Support tab and tick Rescale Support.
- If a specific engineer asked for it, name them and describe the problem briefly.
Support reviews the job and follows up by email.
Un-share once the case is closed, tick the checkbox off on the Support tab.
What to include
Speeds things up considerably:
- The job ID — from the ID column of the jobs list
- What you expected versus what happened
- Which stage failed, if you know — see the job lifecycle
If the status reason is Error executing job. That's a platform-side error and Support will need the job shared to investigate. If it's A run failed, your application returned an error, worth checking logs and exit codes first, since you may not need Support at all.
A Workspace Folder cannot be shared with Support, so batching jobs into a folder does not work here. Share each job Support needs individually.
Sharing a duplicate instead
If you want a colleague to build on your work rather than inspect it, consider having them duplicate the shared job. The duplicate is fully independent, so they can change and rerun it without touching yours.
Related
- Comment on a job — discussion attached to the run
- Reuse a job setup — duplicates and templates
- Find and manage your jobs — the Shared column
- Share a workstation — live session sharing
- Sharing — the general sharing model, including files
- Contact Support — the broader support path
- Workspace Folders — share a whole set of jobs in one action