Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Jobs are categorized based on their operations, ensuring that related operations are grouped together for efficient configuration.
Webhooks can be subscribed to from the category pages within the Job Manager app for specific categories.
Automated messages sent from eCommerce (Shopify) to OMS whenever an event occurs. They contain data about the event and are received in OMS, allowing real time communication between eCommerce and OMS.
Subscribe to Shopify eCommerce Webhooks from OMS for:
Manage pre-configured job automation from Job Details page to streamline operations within the Order Management System.
Every automation task is organized within a dedicated Job Details page, providing a clear overview of job information and actions. This centralized approach ensures quick access to job configurations and facilitates job management.
Clearly identifies the job for easy recognition.
Provides a concise explanation of the job's purpose.
Access a comprehensive job history, including the date, runtime, and status of past runs. The history will display the last 10 records.
Temporarily postpone a job's execution for the upcoming runtime without affecting future scheduled runs.
Permanently stop a job from running further.
Trigger a job to run immediately and resume its scheduled execution pattern afterward.
Set the job's execution time, helping users manage when their scheduled automation.
Set how often the job runs.
Make changes to the job's parameters, settings, or execution details as necessary, allowing users to set up workflows specific to their scenarios. Custom parameters have to be configured before a scheduled job and cannot be changed while a job is pending execution.
Things to remember:
Custom parameters can be incorporated into jobs, with access controlled by specific permissions, ensuring a customized and secure configuration.
Navigate to the required job category and find the job you want to schedule.
Click on the job to view Job Details.
Set the run time.
Set the frequency.
Add custom parameters if required.
Save the changes to see the schedule job on the Pipeline page.
Quickly share the important job related information such as job's ID, name, description, and runtime for debugging.
Discover how HotWax Commerce's Job Manager App streamlines order, product, and inventory operations with its workflow management features.
HotWax Commerce’s Job Manager App enables you to view, schedule, and update job workflows running in the HotWax Commerce's Order Management System for operations related to orders, products, inventory and more.
To directly access the Job Manager application, click on the provided link or navigate to the Launchpad and locate it within the Workflow section.
Learn how to troubleshoot job stuck issues in the HotWax Commerce Job Manager app for seamless job processing.
A scheduled job has been running for a longer duration than expected (more than 15 minutes).
Go to .
Navigate to the status field and click on "Pending."
If there are no jobs in the pending state, it's an unusual situation. Contact HotWax support.
If there are many jobs in the pending state, it indicates a potential backlog in the job queue.
Wait for an hour and then check again if the jobs have run or not.
After waiting, recheck the running tab on the pipeline page. If the jobs have not run, proceed to the next step.
If there are still jobs in the pending state after waiting, contact HotWax support.
Provide details about the extended duration and the number of jobs in the pending state.
By following these steps, you can identify and address issues related to jobs running for an extended duration. If you need further assistance or have additional questions, reach out to the HotWax support team for prompt support.
Job details
Manage pre-configured job automation to streamline operations within the Order Management System.
Initial load
Schedule jobs for the initial deployment and instance setup, tasked with importing all products and orders into the OMS.
Job queueing
View all scheduled, running and completed jobs, with configurations to change the scheduled job data from the Job Pipeline page.
Job categories
Jobs and Webhooks are categorized based on operations, ensuring that related operations are grouped together for efficient configuration.
Bulk job scheduling
Search and select multiple jobs to schedule and execute them collectively for multiple shop configs.
Learn how to troubleshoot issues with scheduling jobs in the HotWax Commerce Job Manager application for seamless job management.
If you are unable to schedule a job in the Job Manager application, and the job data is not appearing, it could be due to missing job draft data, missing job runtime data, or issues with the service in the OMS.
Access the instance web tools using this URL: https://{instance.name}.hotwax.io/webtools/control/FindGeneric?entityName=JobSandbox.
In the JobSandbox form, find the Job Name
field.
Enter the job name you are attempting to schedule.
Move to the "Status Id" field and enter SERVICE_DRAFT
.
Click the search button.
If the job data is not found, it means it's missing, and you need to add it. Refer to the forum post for guidance on how to create and input job data.
In cases where the job draft data is available but scheduling issues persist, follow these steps:
Locate the service name field in the job draft data.
Check if there is data in the service name field.
If not found, contact the HotWax Support team for assistance.
Extract runtime ID
from the job draft data.
Search for the Runtime Data
entity and input the runtime ID in the "Runtime ID" field.
Click the search button.
If no runtime data is found, it is missing. Add runtime data from Webtools: Import/Export page using XML data. Refer to the forum post for guidance on how to input runtime data.
If runtime data is available, and the job is still not executing, the data is incorrect.
Edit the runtime record, scroll down to find runtimeInfo
, and copy the text.
Remove rich text using tools like ChatGPT.
Replace the cleaned data in runtime info and update it.
Retry the job to check if the issue is resolved.
If the problem persists, contact support for further assistance.
By following these steps, you can ensure that the necessary job data is available, allowing you to schedule the job successfully in the Job Manager application.
This document provides a detailed guide to diagnose and resolve the exceptions caused by duplicated jobs in HotWax Commerce, which can lead to data duplication, data redundancy, and system performance issues. The goal is to ensure smooth job execution and accurate data management.
Overlapping jobs causing system performance issues.
Data duplication or redundancy due to duplicated jobs.
Interrupted job flow affecting the order life cycle.
For example, In the Job Manager app, we have two jobs: Approve Order
, which means, approves the orders that are in in created
status after checking the requisite criteria, and Approve Sales Order
, which acts as the same as Approve Order
but has a different attribute (field) values. Let’s suppose we have scheduled the approve orders
job every 5 minutes and approve sales orders
every 15 minutes This collectively means we have two jobs: one is ready to run 5 minutes after the previous run, whereas the other is ready to run from now every 15 minutes. These two jobs will overlap every 15 minutes and may result in system performance issues. Additionally, the collision of these jobs may interrupt the job flow.
Track the Exception:
Identify where the exception occurs or which step of the order life cycle is affected.
Analyze Job Pattern:
Determine if a process is running more than once within its scheduled frequency, indicating a duplicated job.
Access Job Manager:
Open the Job Manager app in HotWax Commerce.
Navigate to the Job Manager > Order
page (for the example provided). For example, If the duplicacy arises in another area like Brokering, navigate to the corresponding section, such as Job Manager
> Brokering.
Identify Duplicated Jobs:
Traverse all jobs and identify those with overlapping schedules. For example, Approve Order
is scheduled every 5 minutes, and Approve Sales Order
is scheduled every 15 minutes.
Duplicated jobs can also be identified by disabling the job with the exception. If the job is disabled once and it is still visible as scheduled after refreshing the page, then the job was duplicated.
Compare Jobs:
Compare both jobs to understand their functionality and attributes.
Disable Duplicated Job:
Terminate or remove the duplicated job causing the exception and the one that is outdated.
Click on the job to open its details.
Click the Disable
button to deactivate the job.
Verify Job Termination:
Navigate to the pipeline
page and search for the disabled job to ensure the problematic job is successfully disabled.
By following these detailed steps, you can effectively troubleshoot and ensure a smooth job execution process, minimize system performance issues, and maintain accurate data management.
If you observe that a process is not functioning correctly in Hotwax Commerce, for example, if orders are not being synchronized, this issue often stems from either the job not being scheduled at all or being incorrectly scheduled. Ensuring proper job scheduling is crucial to maintaining the smooth operation of processes like order synchronization within Hotwax Commerce. This document aims to provide a structured approach for identifying and resolving synchronization issues between HotWax Commerce and external systems due to job scheduling errors.
A job is not scheduled or is disabled, preventing expected data synchronization. For example, the operation team often forgets to schedule the Process Bulk Imported Files
and expects the Import Orders
Job will fetch all the orders from Shopify and start showing them in HotWax Commerce.
A job is not scheduled correctly, causing delays or affecting synchronization. For example, If you schedule a job with a frequency to run with a run-time value(date) of two days later when the job was supposed to run 15 minutes from now, then the job won’t start running in every 15 minutes until 2 days.
Identify the Exception:
Check if a process is not working as expected by looking at the results. If you don't get your desired result within a specified time frame, it indicates an exception.
Backtrack the Exception:
Look into the results in HotWax Commerce OMS to identify the step or task that is not performed.
Access Job Manager:
Open Job Manager using your user credentials.
Navigate to the job causing the issue. For example, if the issue is related to order import(as we see in the above example), go to Job Manager
> Miscellaneous
> Process bulk import files
.
Analyze the Job:
Check if the job is scheduled correctly.
Identify if the job is disabled or configured incorrectly.
Read here to learn more about jobs in HotWax Commerce that can be scheduled as per the retailer’s preference.
Schedule or Configure the Job:
If the job is Disabled
, schedule it by adding the runtime value and the frequency in which the job should run
If the job is configured incorrectly, update it as per your preference. Read here to learn more about how to schedule a job in HotWax Commerce.
Save the Changes:
Make the necessary changes to the job.
Click on the Save Changes
button to ensure they take effect.
Verify Job Schedule:
Check the job schedule on the pipeline
page to ensure the job is scheduled and running at the desired frequency and time.
Monitor Job Execution:
After scheduling or reconfiguring the job, monitor its execution to ensure it runs as expected.
By following these detailed steps, you can effectively troubleshoot and resolve synchronization issues between HotWax Commerce and Shopify caused by jobs not being scheduled or incorrectly scheduled. This ensures smooth job execution, minimizes system performance issues, and maintains accurate data management.
Learn how to troubleshoot failed job issues in the HotWax Commerce Job Manager app.
A scheduled job might fail in HotWax Commerce due to various reasons, such as incorrect parameter settings, outdated information, or conflicts within the system.
Users can swiftly identify the reasons for a failed job from the pipeline
page of the Job Manager
app. This feature allows user to pinpoint the reasons behind failed jobs, facilitating easy troubleshooting of errors. Here's how you can find out the reason behind the failed jobs:
Navigate to the Pipeline page in the job manager.
Within the pipeline page, click on the History tab.
Apply a filter by clicking the checkbox against the Failed option to display only failed jobs.
Click on the Failed badge to view the reason for the failed job.
Common Reasons for Job Failure:
Scheduled jobs can fail due to incorrect parameter settings. If users are facing any issues regarding job configuration, they can follow these steps to rectify the problem:
Step 1: Verify Configuration Data
Search for the job on the pending page in the Job Manager.
You will find the job card with all scheduled job instances.
Pick any instance and open its details.
In the details, find the Custom Parameters
option and click on it to view all custom parameters.
Step 2: Verify Custom Parameters
Verify the custom parameters against the expected values for the service.
You can find the expected custom values in the setup manual for the process you are troubleshooting.
If the parameters are incorrect, proceed to the next step.
Step 3: Disable the Job
Find the job in the category pages and open its detail page.
Disable the job. The custom parameters of a job cannot be edited while it’s running.
Step 4: Correct Incorrect Parameters
Click on "Custom Parameters" and correct the parameters.
Schedule the job again.
Step 5: Check Job Status
After the scheduled time, check the job to see if it has successfully completed. If the job fails, contact the HotWax support team for further assistance.
By following these steps, you can address configuration data issues that may lead to a scheduled job failure. If the problem persists or if you have additional questions, reach out to the HotWax support team for prompt assistance.
Shopify integration issues may arise if Shopify experiences downtime during the day, leading to job failures reliant on accessing its API calls. These failures can be attributed to internal errors within the Shopify platform.
If you encounter any issues with Shopify integration, you can manually run the job by clicking on the Run Now
button or wait for the next scheduled job to resolve the problem.
In job scheduling systems, a semaphore could be used to manage the allocation of resources (like CPU time, memory, or disk space) among competing processes or jobs. This ensures that resources are efficiently utilized and that no single job monopolizes Semaphore issues in job scheduling can lead to various consequences when a job fails. These include resource starvation, deadlocks, performance degradation, job abandonment, and system instability. These issues can result in failed or incomplete tasks, resource contention, and system-wide slowdowns, emphasizing the importance of proper monitoring and mitigation strategies. If you encounter any issues with semaphore, you can manually run the job by clicking on the Run Now
button or wait for the next scheduled job.
Manage all pending, running, and completed jobs from the Pipeline page. With intuitive controls and detailed job information, you can effectively monitor and manage job execution.
Pipeline page
Provides a holistic view of all jobs, including their status, scheduled time, and execution details.
Characteristics
Chronological sequence for prioritized execution
Jobs are displayed in chronological sequence, ensuring that jobs with the closest expiration time are prioritized for execution.
Timeline Visualization for Clear Execution Scheduling
A highlighted time frame clearly depicts the job's runtime and scheduled frequency, providing a visual representation of the job's execution timeline.
On-the-fly Editing for Dynamic Job Management
Users can seamlessly skip, cancel, edit, or reschedule any pending jobs before they start running. This flexibility allows users to adapt to changing requirements and optimize job execution based on real-time needs.
Customized Job Configurations for Tailored Execution
Scheduled job parameters can be modified directly from the Job Pipeline page, enabling users to tailor job execution to specific needs. This flexibility allows for optimization of job performance and resource utilization.
Detailed Job History for Analysis and Troubleshooting
Comprehensive historical job data is readily accessible for analysis and troubleshooting purposes. Users can identify patterns, optimize job performance, and resolve recurring issues by examining historical job execution details.
Displays all the jobs queued for execution.
Displays all the jobs running in the system.
Displays all the historical jobs. Historical jobs can be filtered by their status.
Easily locate specific jobs by name or category.
Quickly find jobs by applying filters based on category and status.
Keep frequently accessed jobs readily available for quick access. Pinned jobs will be visible in the footer.
Displays the number of counts the job is retried once failed.
Effortlessly schedule and manage bulk jobs with ease. Configure, select, and streamline workflows seamlessly.
Displays configurations to schedule jobs in bulk.
Manage Jobs
Easily search and select the jobs you want to execute or configure. You can also schedule jobs and set their run times.
Schedule Jobs
Conveniently configure and schedule all selected jobs simultaneously to streamline your workflow.
Product store
If your OMS is connected to multiple eCommerce stores selling different collections of products, you may have multiple Product Stores set up in HotWax Commerce.
eCom stores (Shopify Configs)
If your OMS is connected to multiple eCommerce stores selling the same catalog operating as one Company, you may have multiple Shop Configs for the selected Product Store.
Select jobs
Search Jobs and use the Add function to select jobs to be scheduled.
Scheduler
Configure and schedule all selected jobs simultaneously.
Scheduled run time and frequency, set on bulk scheduler, will be applied to all the selected jobs.
Choose the Product store.
Select the relevant Shopify configurations.
Click Select Jobs
function to proceed to locate and add the jobs you wish to schedule.
Adjust the scheduled run time and frequency according to your requirements.
Schedule jobs responsible for importing all products and orders into the system for the initial deployment and instance configuration from the Initial Load category.
Displays the jobs for initial OMS setup to import all products and orders.​
Characteristics
One time ExecutionThese jobs are executed only once during the initial setup and rarely during instance redeployments.
Product and Order Importation
Facilitate the importation of all products and orders from the eCommerce platform for the initial instance setup.
Scheduling Functionality
Empower users to schedule the import process, enabling them to select the desired execution time.
Things to remember:
Products should be imported before any order is imported into the system.
By default only open and unshipped orders will be imported.
The Last Shopify Order ID serves as a reference point for HotWax Commerce to determine the starting point for order downloads.
Go to the Initial Load category.
Initiate the Import Products in Bulk
job.
Choose the desired runtime from the dropdown menu.
Confirm the selected runtime.
Go to Miscellaneous Jobs page.
Initiate the Process bulk imported files
job.
Once product importation is complete, proceed to the Import Orders in Bulk
job.
Select the preferred runtime from the dropdown menu.
Verify the order and fulfillment status.
Input the Last Shopify ID from which order numbers should be imported into HotWax Commerce OMS.
Execute the import process.
Go to Miscellaneous Jobs page.
Initiate the Process bulk imported files
job.