web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested answer

Import job stuck in 'Not run' status

(0) ShareShare
ReportReport
Posted on by 11,633

Hi All,

I am trying to update the email addresses for Workers using Worker data entity. Previously, I have uploaded new worker using the same data entity and it worked fine, but this time it stuck in 'Not run' status, even though I clicked the Import button. I have clicked Refresh several times, but no luck.

Has anyone experienced similar issue before and can guide me how to resolve this issue ?

Thanks,

Baber.

I have the same question (0)
  • Suggested answer
    Sergei Minozhenko Profile Picture
    23,093 on at
    RE: Import job stuck in 'Not run' status

    Hi Baber,

    Does the issue appear in the production or sandbox or development environment? If it's sandbox or dev, I suggest checking if the DIXF service is up and running. Also, you check if you see anything in the event logs.

  • Suggested answer
    André Arnaud de Calavon Profile Picture
    299,349 Super User 2025 Season 2 on at
    RE: Import job stuck in 'Not run' status

    Hi Baber,

    In the past, I did experience also issues with the Worker data entity. If you are running the update using the batch framework, might be more stable compared to run it directly.

    How many records do you have in this entity? In my scenario, I also had to update just one field for 1400 workers. I ended up in creating a Flow using Microsoft Power Automate. It took 1 second to read the Excel file, but processing each records was very slow. After some hours, the flow completed and the data was updated. So, Microsoft Power Automate might be a workaround here.

  • Suggested answer
    Community Member Profile Picture
    on at
    RE: Import job stuck in 'Not run' status

    Hi Baber,

    you DIXF service is probably not running. also check if your environment is not in Maintenance mode.  

  • syed baber Profile Picture
    11,633 on at
    RE: Import job stuck in 'Not run' status

    Hi Andre,

    I used Excel Add-in now to update the email addresses for specific workers and publish the records. It worked so well without any issues.

    Thanks,

    Baber.

  • Suggested answer
    Community Member Profile Picture
    on at
    RE: Import job stuck in 'Not run' status

    Hi Baber,

    Excel Add-in uses the OData endpoint and doesn't go through or utilise the DIXF service.

    1. Validate DIXF service is running.
    2. Check if maintenance mode is enabled or not.
    3. Try Import in batch option.

    You can check if "License Configuration" form is opening as read-only or in edit mode. If in edit mode, then your maintenance mode is ON.

  • André Arnaud de Calavon Profile Picture
    299,349 Super User 2025 Season 2 on at
    RE: Import job stuck in 'Not run' status

    Hi Baber,

    If the question has been answered, would you mind to mark the correct answer? The thread will then get the status answered and other users with the same question will be directed to the verified answer(s).

  • Suggested answer
    syed baber Profile Picture
    11,633 on at
    RE: Import job stuck in 'Not run' status

    Hi Andre,

    It seems like the job stuck in 'Not run' status, because around that time in Production, so many jobs were in Executing state in Production due to deadlocks. I don't see any other reason for this. So, in my opinion, if this happens, one needs to check if there are any deadlocks in the system and check number of batch jobs in executing state.

    Can't try this one more time, as the data has already been updated in Production.

    Thanks,

    Baber.

  • André Arnaud de Calavon Profile Picture
    299,349 Super User 2025 Season 2 on at
    RE: Import job stuck in 'Not run' status

    Hi Baber,

    If you do see deadlocks, you have to find out the head blocker, next time. Then it would be possible to analyze what is causing it.

  • syed baber Profile Picture
    11,633 on at
    RE: Import job stuck in 'Not run' status

    Hi Andre,

    I did find the head blocker and kill it, but I didn't know that there are deadlocks in the system when I was running data import, until the customer reported that.

    Thanks,

    Baber.

  • André Arnaud de Calavon Profile Picture
    299,349 Super User 2025 Season 2 on at
    RE: Import job stuck in 'Not run' status

    The head blocker contains a certain SQL statement. From there, you can see if there is something wrong in a certain process. Probably due to  wrong coding, a report with a long running query might block the full table for other users.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 2,100

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 890 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 633 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans