> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/system-admins/administration/company/manage-sync-jobs.md).
# Manage sync jobs in Company
Review and manage service jobs from Company sync pages.
Company's product, inventory, order, fulfillment, transfer, and onboarding pages can open a shared job dialog. Use it to review a specific service job before changing a schedule or starting a run.
## Confirm job identity and scope
1. Open the configured job from the relevant sync page.
2. Confirm the internal job name in the dialog title.
3. Review the description, service, and parameters.
4. Check whether the job serves one shop, product store, inventory channel, or the whole HotWax Commerce instance.
If `Sync job details unavailable` appears, select `Retry` or use the refresh action. A failed load does not mean the job is absent. Run and save actions require a successfully loaded job.
Review the selected job's service, schedule, execution time zone, and typed parameters before changing or running it.
## Review a schedule
Open `Schedule` to review the cron expression, its description, execution time zone when supplied, and next run. The schedule description uses the job's execution time zone; do not assume it is the browser time zone.
Changing a schedule draft displays `Next run recalculated after saving` until it is saved. A manual job can legitimately show `Not scheduled`.
## Save changes
1. Change `Active`, the schedule, or the editable parameter values required by the task.
2. Review the scope and draft values.
3. Select the save action.
4. Verify the reloaded job.
Scope-defining parameters, such as the shop, product store, and channel, normally remain read-only. A page can permit a specific scope parameter for a manual recovery job; review that scope before running it.
A changed schedule must be valid before saving. A manual job without a schedule can still save permitted parameter changes. Closing or refreshing with unsaved changes asks whether to discard them.
If a save partly succeeds, keep the dialog open and retry only the remaining draft changes. Do not assume that an error means no configuration changed.
## Run and verify a job
`Run now` starts an immediate execution using the saved job configuration and does not change its schedule. Save intended configuration changes first, check for an existing active run, then run only for an approved operational purpose.
Review the run result and error information. A request being accepted is not proof that synchronization completed. Use `Recent runs` and `View all runs` to follow the execution; verify the affected Shopify or HotWax Commerce records before considering the task complete.
The dialog previews five recent runs and ten edit-history records. Use `View all runs` or Job Manager when you need more history or need to investigate overlapping jobs.
## Related guides
* [Monitor Shopify Product Sync](/documents/system-admins/administration/company/manage-shopify-shop/manage-shopify-product-sync.md)
* [Monitor Shopify inventory sync](/documents/system-admins/administration/company/manage-shopify-shop/manage-shopify-inventory-sync.md)
* [Manage Shopify Order Sync](/documents/system-admins/administration/company/manage-shopify-shop/manage-shopify-order-sync.md)
* [Manage a job in Job Manager](/documents/system-admins/administration/job-manager/jobs/job-details.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.hotwax.co/documents/system-admins/administration/company/manage-sync-jobs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
