In HotWax Commerce, jobs are pivotal for executing various operations like data importing or exporting. Each job comprises two essential components: service and runtime. The service component determines which service will execute the job operation, while the runtime component configures job details such as scheduling and frequency. Services are stored in the service engine, while runtime data resides in a separate entity known as runtimedata. The combinations of runtime and service are stored in the jobsandbox entity, which creates a draft job for every scheduled job, serving as a benchmark copy for new job runs.

One of the issues encountered in HotWax Commerce Job Management is the occurrence of runtime configuration errors, disrupting the scheduling and execution of jobs. These errors stem from the corruption of runtime data, resulting in incorrect job configurations and subsequent failures during execution.

Troubleshooting Steps:

1. Access Webtools: Navigate to the webtools section of your specific HotWax Commerce instance.

2. Open Entityengine: Within webtools, locate and click on entityengine.

3. Find Jobsandbox Entity: In the entityengine menu, locate the jobsandbox entity.

4. Search for Job: Use the search functionality within the jobsandbox entity to find the job with the relevant jobid. Set its status as service_draft.

5. View Job Details: Once you've located the job, you'll see a table displaying various details, including the runtime ID of the job.

6. Navigate to Runtimedata: Return to the entityengine menu and search for the runtimedata entity.

7. Check XML Content: Within the runtimedata entity, locate the entry corresponding to the runtime id of the job. Check the XML content associated with it.

8. Modify XML Data: Using appropriate tools, extract the XML data and remove any extraneous content or rich formatting. You can utilize generative AI tools like ChatGPT for this purpose.

9. Update Runtime XML: Paste the refined XML data back into the runtimeid field of the job entry within the jobsandbox entity.

10. Save Changes: Confirm the changes and save the updated runtime data.

11. Schedule the Job: With the runtime data corrected, you can now successfully schedule the job without encountering any runtime configuration errors.

By following these steps, users can efficiently rectify runtime configuration errors within the HotWax Commerce platform, ensuring uninterrupted job scheduling and smooth workflow operation.

If the time zone settings for the instance’s server and scheduled jobs do not match, it can lead to data time discrepancies between Hotwax Commerce and Shopify. For example, let’s say a customer placed an order on Shopify today, but after importing, when you look at the Hotwax Commerce Sales Orders page, the order date appears as yesterday. The reason behind this discrepancy is the mismatched time zone between the Hotwax Commerce instance and the scheduling time zone of the Import Orders job.

Steps to Diagnose and Resolve the Issue

Verify the Discrepancies

1. Check the Time Zones in the Job Sandbox Entity:

   • Visit: https://{instance}.hotwax.io/webtools/control/FindGeneric?entityName=JobSandbox

   • Ensure the Recurrence time zone in the Job Sandbox entity matches the instance’s Server time zone.

2. Check the Instance’s Server Time Zone:

   • Navigate to: Hotwax Commerce OMS > Dashboard > About
   • Verify the instance’s Server time zone.

Adjust the Time Zone for the Job

1. Open the Job Manager Application:

   • From the launchpad, open the Job Manager application in Hotwax Commerce.

2. Navigate to Settings:

   • Click on Settings within the Job Manager.
3. Change the Selected Time Zone(If required):

   • Navigate the App section within the settings.
   • Identify the two time zones:

     • Browser Time Zone

     • Selected Time Zone

   • Adjust the Selected Time Zone to match the instance's Server time zone (if necessary).
4. Save Changes to the Job (Using JOB_IMP_ORD as an Example):

   • Navigate to Orders in the left menu.
   • Go to New Order under the import section inside Orders.
   • Inside the Import Order box, find and click on SAVE CHANGES at the bottom right of the same job.

By following these steps, you can correct the time zone settings and resolve the time mismatch issue between Shopify and Hotwax Commerce. This will ensure that data is consistent and accurate across both platforms, enhancing the reliability of order management system.

In HotWax Commerce, two types of services handle data processing: Order Management System (OMS) jobs and NiFi jobs. Understanding the runtime and scheduled frequency of these jobs is crucial for maintaining smooth operations.

Checking OMS Job Frequencies

OMS jobs manage core functions such as product, order and inventory data imports and exports. When these jobs do not run as scheduled, it can disrupt operations and cause data inconsistencies.

1. Verify Job Existence:

   • Navigate to the Job Manager app in HotWax Commerce.

   • Go to the relevant page (e.g., Orders, Inventory).

   • Locate the job by its name and description.

2. Check Job Schedule:

   • Identify the schedule of the job listed against its name.

   • Click on the job card to view job details.

3. Review Job History:

   • Click on the history text to ensure the job is running at the scheduled frequency.

Checking Napita Job Frequencies

Napita jobs manage data flows and data transformations between HotWax Commerce and External Systems. When these jobs do not run as scheduled, it can affect data synchronization and integration.

1. Open Relevant Napita Instance:

   • Access the Napita instance associated with your HotWax Commerce OMS.

2. Navigate to Parent Processor Group:

   • Find the parent processor group for your OMS instance.

   • Drill down through the processor groups to locate relevant processors.

3. Locate Relevant Processor Groups:

   • Enter the processor groups until you find the relevant processors with flowfiles.

4. Check Processor Scheduling:

   • Identify the first processor with the scheduling expression.

   • Note the cron-driven expression for the first processor.

5. Convert and Verify Cron Expression:

   • Use a cron expression generator or ChatGPT to convert the cron format and verify the schedule.

6. Review Processor Settings:

   • Ensure each processor is set to the correct schedule.

   • Verify that subsequent processord are time-driven and have the appropriate schedule after concurrent tasks.

Common Issues and Fixes:

• Incorrect Cron Expression:

  • Verify and correct the cron expression using a converter tool.

  • Ensure the expression matches the desired schedule.

• Processor Scheduling Errors:

  • Check each processor's scheduling settings.

  • Adjust schedules to ensure proper timing and concurrency.

By following this guide, you should be able to diagnose and resolve job frequency issues within HotWax Commerce, ensuring smooth and efficient data processing.