There are a few reasons a scheduled data job may not execute. I made a silly mistake and it seemed as though the jobs where stuck on “In process”.
Things I checked:
1. Check the job isn’t disabled. See screenshot below. There is a toggle.
2. Check your recurring batch job is scheduled
3. Check you haven’t made any mistakes when enqueuing the entity. (I made a typo here)
I made the mistake of copying the URL and not changing the entity name. See the highlighted part in the url.
https://myenviornment.cloudax.dynamics.com/api/connector/enqueue/123456789-5506-4314-874D-3CF51A7AE15A?entity=General%20journal&company=usmf
Things I checked:
1. Check the job isn’t disabled. See screenshot below. There is a toggle.
2. Check your recurring batch job is scheduled
3. Check you haven’t made any mistakes when enqueuing the entity. (I made a typo here)
I made the mistake of copying the URL and not changing the entity name. See the highlighted part in the url.
https://myenviornment.cloudax.dynamics.com/api/connector/enqueue/123456789-5506-4314-874D-3CF51A7AE15A?entity=General%20journal&company=usmf
Below is a screenshot of the record info. You can see the Entity field contains the string I passed via the enqueue URL.
Sounds pretty simple but hopefully helps someone out there.
There are a few reasons a scheduled data job may not execute. I made a silly mistake and it seemed as though the jobs where stuck on “In process”.
Things I checked:
1. Check the job isn’t disabled. See screenshot below. There is a toggle.
2. Check your recurring batch job is scheduled
3. Check you haven’t made any mistakes when enqueuing the entity. (I made a typo here)
I made the mistake of copying the URL and not changing the entity name. See the highlighted part in the url.
https://myenviornment.cloudax.dynamics.com/api/connector/enqueue/123456789-5506-4314-874D-3CF51A7AE15A?entity=General%20journal&company=usmf
Things I checked:
1. Check the job isn’t disabled. See screenshot below. There is a toggle.
2. Check your recurring batch job is scheduled
3. Check you haven’t made any mistakes when enqueuing the entity. (I made a typo here)
I made the mistake of copying the URL and not changing the entity name. See the highlighted part in the url.
https://myenviornment.cloudax.dynamics.com/api/connector/enqueue/123456789-5506-4314-874D-3CF51A7AE15A?entity=General%20journal&company=usmf
Below is a screenshot of the record info. You can see the Entity field contains the string I passed via the enqueue URL.
Sounds pretty simple but hopefully helps someone out there.
There are a few reasons a scheduled data job may not execute. I made a silly mistake and it seemed as though the jobs where stuck on “In process”.
Things I checked:
1. Check the job isn’t disabled. See screenshot below. There is a toggle.
2. Check your recurring batch job is scheduled
3. Check you haven’t made any mistakes when enqueuing the entity. (I made a typo here)
I made the mistake of copying the URL and not changing the entity name. See the highlighted part in the url.
https://myenviornment.cloudax.dynamics.com/api/connector/enqueue/123456789-5506-4314-874D-3CF51A7AE15A?entity=General%20journal&company=usmf
Things I checked:
1. Check the job isn’t disabled. See screenshot below. There is a toggle.
2. Check your recurring batch job is scheduled
3. Check you haven’t made any mistakes when enqueuing the entity. (I made a typo here)
I made the mistake of copying the URL and not changing the entity name. See the highlighted part in the url.
https://myenviornment.cloudax.dynamics.com/api/connector/enqueue/123456789-5506-4314-874D-3CF51A7AE15A?entity=General%20journal&company=usmf
Below is a screenshot of the record info. You can see the Entity field contains the string I passed via the enqueue URL.
Sounds pretty simple but hopefully helps someone out there.
.webp)
0 Comments