We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Troubleshooting 'Action strategy job trigger failed' error message

Bhuvana Venkate
Tera Contributor

I am running 'GAF - Run Offline Flow job' and getting the error message 'Action strategy job trigger failed' and it stops at 70% progress. Has anyone encountered this error? Any suggestion for the troubleshooting?

 

Please guide/help.

5 REPLIES 5

Learnerk
Tera Contributor

We are facing the same issue here. Could you let me know if you found a solution?

Paulsylo
Tera Sage

Have you tried cancelling and rerun the job manually ? it fixes this trigger failed issue. 

Regards,
PaulSylo

To be is to do. To do is to be.

rpriyadarshy
Kilo Sage

@Bhuvana Venkate  Check these steps

 

  • Ensure that both the groupSkillID and actionSkillId variables are correctly populated in your background script before running the job. Missing or incorrect values will cause the job to fail .
  • Verify that the filter condition in your Grouping inputs returns at least 2,000 records. If the filter yields too few records, the job will fail during the training phase .
  • Check the sn_gaf_sysauto_script table for a valid GAF Job tracker record. The most recent record should show the state as "Offline job complete" for the "GAF - Run Offline Flow" job.
  • Review the ml_solution table for a record with a training solution name like "ml_x_snc_sn_itsm_aia_global_incident_clustering_" and ensure its state is "Solution Complete" with progress at 100%. If the state is "Unauthorized" or "Error while training the solution," you may need to open a case with Now Support .
  • If you see the error "All skills need to be activated in order to set up GAF," make sure all required skills are activated and their sys_ids are correctly referenced.

Regards

RP

Hi @rpriyadarshy - these are general troubleshooting steps, but the when the progress got hanged, either running scheduled are overlapped or script running against a older version, so stop the process and re run this manually will fix the issues,

Regards,
PaulSylo

To be is to do. To do is to be.