Manage the synchronization job
Check, pause, and recover the recurring NTMP job queue entry.
The background job processes Pending NTMP sync records. Installation attempts to create it with a five-minute recurrence.
Identify the job
Search for Job Queue Entries and locate:
| Setting | Expected value |
|---|---|
| Description | NTMP auto-sync to the tourism portal |
| Object Type to Run | Codeunit |
| Object ID to Run | 70011017 |
| Recurring Job | Enabled |
| No. of Minutes between Runs | 5 |
Confirm the job can run under a user with appropriate integration and Business Central permissions. The schedule depends on the job being ready and the environment's background processing being available.
If the job is missing
Open NTMP Settings and choose Start Auto-Sync. Return to Job Queue Entries to confirm the job was created and is ready.
If the job is on hold or in error
- Open the existing job and inspect its status and error log.
- Fix the cause, such as an unreachable server or missing connection setting.
- Use the standard job queue actions to restart it or set it ready.
- Review NTMP GL Sync after the next run.
Start Auto-Sync leaves an existing entry unchanged; it does not clear errors or release an existing hold.
Pause scheduled sending
Put the job On Hold and allow any in-progress run to finish. New eligible postings may still queue locally. Avoid Process Now while you intend sending to remain paused, because it processes pending records independently of the schedule.
Pending rows after a job error
A connection exception can stop the run without marking the affected record Failed. Review both the job log and the Pending queue. Failed rows, by contrast, need Retry before the job will process them again.