Privacy & troubleshooting · All applicants
What to do when Job Loop preparation stops
If preparation stops or only some documents are ready, open the run history to see what finished and what needs attention. You may be able to review a completed document, resolve an issue and resume, or cancel the remaining work. Start with the recorded status and the message beside it.
What to take with you
- Read the recorded status and messages.
- Review existing outputs independently.
- Distinguish cancelling a run from cancelling a schedule.
Inspect the current record first
Open Run history and source coverage in Job Loop and read the status, current step and messages. Check which sources completed and which need attention. If you have just selected an action, refresh the records to see its result before deciding what to do next.
Write down the specific unfinished step. It may concern a source, configuration, a budget stop or preparation. Avoid reducing every interruption to 'the app failed'. A precise observation helps you decide whether there is useful output to review and gives support a clearer description if you need assistance.
Source for the published guidance: Jobvance: How the application workflow works.
Separate run completion from packet approval
A run's status and a packet's approval are different. Existing packets may require review even when a run completed. A partial run may have produced some outputs while leaving another stage unresolved. Open the recorded outputs and inspect their source facts, vacancy connection and status. Do not assume they are ready because they exist.
Check whether the underlying career facts or vacancy have changed since preparation. A previous approval should not justify downloading a document based on stale information. Review the current packet and its available actions. If something is incomplete or unavailable, keep that limitation visible rather than rebuilding a missing section from guesses.
Confirm cancellation at the right scope
Use a run's Cancel run control when you want to stop that preparation request, then check the recorded state. A schedule has its own pause and cancellation controls. Pause schedule stops future scheduling and retains the current run. Cancel schedule also stops its latest queued or running scheduled job. It does not cancel a separate manual run. Refresh both records to confirm what stopped.
Cancellation is also separate from deleting saved data or recalling external copies. Previously downloaded documents or drafts already created in another service need their own review. Do not treat a cancellation confirmation as proof that all source records, outputs and external drafts were erased. Use the relevant privacy or account process for an erasure request.
A candidate cancels a weekly schedule while a preparation run is active. The schedule also cancels its latest queued or running scheduled job. They refresh the run history to confirm this and separately inspect any manually started run. One previously prepared packet remains visible, so they review it as an existing output rather than assuming it was submitted or deleted. No application was sent by the run.
Resume only after understanding the stop
If the interface offers Resume run, read the messages first and resolve any indicated prerequisite. Confirm your career record is saved and the current source information is appropriate. Available actions depend on the run state and configured capabilities. Do not repeatedly start new runs because one request has not yet shown a result.
When the same issue persists, stop blind retries and collect a minimal support note. Include the approximate time, run identifier if shown, status, phase and message. Leave raw CV text, private email contents and sensitive documents out unless a secure support process specifically needs them. A precise description is usually more useful than a large attachment.
Choose one next action
There are three useful paths: review a completed output, resume an eligible run after resolving the issue, or request help with the recorded problem. Choose the one supported by the interface. A run being partial does not establish that your application is weak; it describes the preparation process, not an employer decision.
Open your Job Loop to inspect history, or use the public contact page for general help without adding private material. If you simply need to prepare one CV while a connection is unavailable, the free check offers a separate review path. Approve the result yourself and submit through the employer's channel when the packet is ready.
Sources and further reading
The links support the specific guidance cited above. Our checklists and worked examples show how to put the guidance into practice. Read current official requirements before acting.