Showing results for 
Show  only  | Search instead for 
Did you mean: 


FNMS to ServiceNow Export stuck in Waiting state for scoped app 5.0.854. Take note that you won't notice the issue if you are only doing one of the following exports: HW, Apps, or Contract.

However, if you run all 3 or just 2. The second Import Run will always get stuck in Waiting state.

Replication Scenario

  1. Use Flexera integration scoped app 5.0.85

  2. Set Up FNMS to ServiceNow exports outlined on this docs:

  3. Run a full export


Do this first, if you have stuck import runs in ServiceNow.

  1. In ServiceNow, browse to 'Scripts - Background'
  2. Copy & Paste the contents of CleanupHungImport.txt
  3. Change in scope to 'x_fls_flexera_fnms'
  4. Run the script

Once verified all stuck import runs and transactions have been set to fail. 

Implement hotfix SN-1104

  1. Extract contents of Flexera Integration
  2. In ServiceNow, browse to Retrieved Update Set
  3. Import XML hotfix -> Preview Update Set -> Update Set Commit

Version Fix Target

Flexera Integration scope app 5.0.9xx


Was this article helpful? Yes No
No ratings
Level 6

You also should be sure to change developer rights under the Flexera app in ServiceNow when you run the cleanuphungimport script:

  1. Within ServiceNow click on “Settings” and then set the “Developer” context to “Flexera Integration”.
  2. Within ServiceNow search for “Flexera Integration” and then select “Fix Scripts”.
  3. Click “New”.
  4. Set the “Name” and “Description” and then copy the contents of “CleanupHungImport.txt” in the “Script” field.
  5. Validate the entries and select “Submit”.
  6. Validate that “CleanupHungImport” fix script has been added.
  7. Elevate your roles by clicking on your account and selecting “Elevate Roles”.
  8. Select “security_admin” and click “OK”.
  9. Click “Run Fix Script”.
  10. Select “Proceed in Background”.
  11. In ServiceNow search for “Progress” and select “Progress Workers”. Find and select the job you just ran.
  12. Validate the status of the script.
Level 2

I was experiencing this only running the Computer export however this hotfix has fixed my problem.

Version history
Last update:
‎Jun 30, 2022 02:34 PM
Updated by: