You’re offline. This is a read only version of the page.
Announcements
20
Unable to create any new customers in BC after installing 20.5, just get the following error everytime -
Any ideas?
Hi again,
I have received this answer from MS:
CRM integration jobs can be in two states other than Running and Error: Ready and On Hold with Inactivity Timeout.
If a job is in Ready state, next run will be calculated by "No. of minutes between runs".
If a job is in On Hold with Inactivity Timeout state, next run will be calculated by "Inactivity Timeout Period".
A CRM integration job will be put in On Hold with Inactivity Timeout state if the last job didn't synchronize any records (meaning there were no changes at all).
Final and very important note, a job in On Hold with Inactivity Timeout state will be woken up if there's a change (create new record, modify existing record, delete existing record). For example, CUSTOMER-ACCOUNT job will be woken up if there's any change made to customer records in Business Central.
This would mean that integration jobs are activated from the "On Hold with Inactivity Timeout" state whenever a change is made, so there should never be a long wait between runs at all. I have not yet been able to verify this myself, as we have now equated the timeout period with the time between runs for these jobs. We do not need the runs to be < 5 minutes.
Maybe this information will help.
Hi Gunter,
that is interesting to know, we actually need a near real-time generation of the invoices, so we have the sync jobs set to run every 1 minute (then a SO posting job too). The minimum timeout period is 5 mins , I dont want to set the run interval to 5 mins to match if that is going to cause delays.
bug or feature indeed!
Hi,
I have the same problem, but was able to find a workaround.
It is related to the parameter "Inactivity Timeout Period".
Until 20.5, the field "Earliest Start Date/Time" was recalculated after an execution using the parameter "No. of minutes between runs". Now it seems that the parameter "Inactivity Timeout Period" is used for this.
I set these two parameters to the same value for all jobs and, lo and behold, they run again as usual at the defined intervals.
I hope this helps pass the time until MS fixes the bug. Or is this a new feature?
BR
Gunter
Hi,
This seems to have sorted that issue, but we are having no end of issues with the job queue not triggering the recurring jobs. No job seems to be going on hold with inactivity correctly, none are actually triggering on the schedule, just running at random intervals and then some fall out of running at all when the earliest start date is in the past (but then sometimes run anyway).
Hello,
This is a confirmed bug and fixes have been created since we got to it. The fixes or repair items will resolve the issue. As soon as the hot fix reaches your tenant, the scenario is resolved.
Thank you for mentioning this to us on the forum.
Yes was working fine before. Looked at the customer template and it’s empty, but adding the no series there makes no difference. I can create a new customer manually and it works fine even with the no séries empty in the template. It seems to be whatever the job queue is looking at is different to everything else. but don’t know where to define the no series for the job? Do you know? Thanks
Hello,
Interesting, did this work before with 20.4 and after upgrade this fails. Is there a number series for Customers?
Thank you.
#1
André Arnaud de Cal...
294,069
Super User 2025 Season 1
#2
Martin Dráb
232,858
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
