Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Unanswered

Known Bug in Field Service v8.8.22.57 - Infinite Loop Error on Agreements

(0) ShareShare
ReportReport
Posted on by 721

A bug was introduced in Field Service v8.8.22.57 that affects the automatic generation of Agreemetn Work Orders and Invoices. I have copied and pasted the information below as it was provided by Microsoft in the Office365 Message Center.

_________________________________________________________________________________________________________________

We would like to raise your awareness to a potentially disruptive bug that our telemetry indicates has impacted your environment.

 

Scope of Issue:

 

When Dynamics 365 Field Service v8.8.22.57 installed, a bug was introduced that may have impacted your agreements. Depending on the geography of your environment, the solution containing this issue was installed within the last month.

 

 

This issue potentially impacts generation of:

  • Work Orders
  • Invoices
  • Agreement Booking Dates
  • Agreement Invoice Dates

 

How does this affect me?

 

You may have Work Orders, Invoices, Agreement Booking Dates, and/or Agreement Invoice Dates which have not been generated.

 

 

How to resolve the issue?

 

To resolve this issue, you can either follow the below steps on your own or contact support and we will walk through the following steps with you. If you create a support request, please highlight that this is related to "Field Service - Infinite Loop Error on Agreements."

 

  1. Go to Admin Center and ensure your environment has been upgraded to the latest version of FS which contains a fix for this issue. While we created and deployed a fix for this issue as soon as possible, in some geographies, this fix has not yet been automatically-deployed. (If you do not see an available upgrade, the solution with this fix has already been deployed on your environment. FS v8.8.22.58 and v8.8.23.85 both contain the fix for this issue.)
    _______________________________________________________________________________________
     
  2. It is possible that some Work Orders which should have generated have been missed and are in a state that may cause them to not be automatically regenerated. If you would like to retroactively generate WOs for the impacted Agreement Booking Setups, create the following advanced find:

 

  1. On Agreement Booking Date, start with the saved view "Active Agreement Booking Dates":
    1. Status Equals Active
    2. Booking Date On or Before "Today's date value"
    3. Linked related Booking Setups which contain data
      1. Linked related System Jobs which contain data
        1. Status Reason Equals Failed
        2. System Job Name Begins With "Field Service"
        3. Completed On Last X Days 30


Based on the results of this query, highlight each Agreement Booking Date for which you want to generate a Work Order which is for today or in the past then push the "Generate WO" button in the command bar.

Note: Do this step before moving on if you wish to generate the missing WOs. Once you begin the next step, you will be unable to generate these records as the Agreements processes will delete the unprocessed Agreement Booking Dates that may have been missed and they will only be regenerated for future dates.
______________________________________________________________________________________________________________
 

  1. To identify and reinitiate processes related to your impacted Agreement Booking records, create the following advanced find:
     
    1. On the Agreements entity, start with the saved view “Active Agreements”:
      1. Status = Active
      2. System Status = Active
      3. Linked related Agreement Bookings which contain data:
        1. Linked related System Jobs which contain data:
          1. Status Reason = Failed
          2. Friendly message contains “This workflow job was canceled because the workflow that started it included an infinite loop. Correct the workflow logic and try again. For information about workflow logic”
          3. Created On Last X Days 30


Based on the results of this query, highlight each Agreement for which you need to reinitiate the failed processes which control Agreement Booking Date creation and subsequent Work Order creation.
 

  1. Bulk Edit the selected Agreements:
    1. Click Edit.
    2. Set the “System Status” field to Estimate.
    3. Click Change.
    4. All Agreements will disappear from your advanced find, since they now have a System Status set to Estimate.
       
  2. Edit your advanced find parameters to change System Status = Active to System Status = Estimate.
    1. Execute the query.
    2. Select all returned Agreements to once again Bulk Edit records.
    3. Click Edit.
    4. Set the System Status field to Active.
    5. Click Change.


Note: While background processes are running, you may not be able to change the state again, immediately. Wait a moment and try to save to active, again.
______________________________________________________________________

 

  1. To identify and reinitiate processes related to your impacted Agreement Invoice records, create the following advanced find:
     
    1. On the Agreements entity, start with the saved view “Active Agreements”:
      1. Status = Active
      2. System Status = Active
      3. Linked related Agreement Invoices which contain data:
        1. Linked related System Jobs which contain data:
          1. Status Reason = Failed
          2. Friendly message contains “This workflow job was canceled because the workflow that started it included an infinite loop. Correct the workflow logic and try again. For information about workflow logic”
          3. Created On Last X Days 30


Based on the results of this query, highlight each Agreement for which you need to reinitiate the failed processes which control Agreement Booking Date creation and subsequent Work Order creation.
 

  1. Bulk Edit the selected Agreements:
    1. Click Edit.
    2. Set the “System Status” field to Estimate.
    3. Click Change.
    4. All Agreements will disappear from your advanced find, since they now have a System Status set to Estimate.
       
  2. Edit your advanced find parameters to change System Status = Active to System Status = Estimate.
    1. Execute the query.
    2. Select all returned Agreements to once again Bulk Edit records.
    3. Click Edit.
    4. Set the System Status field to Active.
    5. Click Change.


Note: While background processes are running, you may not be able to change the state again, immediately. Wait a moment and try to save to active, again.

Re-triggering these processes will retroactively generate Invoices which may have been missed.

 

If you require further assistance, please reach out to Microsoft Support and use the keywords "Field Service – Infinite Loop Error on Agreements" for their assistance in navigating this process.

  • Anthony Dong Profile Picture
    on at
    RE: Known Bug in Field Service v8.8.22.57 - Infinite Loop Error on Agreements

    hi,

    Thanks for your great sharing !!!

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

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Jonas ”Jones” Melgaard – Community Spotlight

We are honored to recognize Jonas "Jones" Melgaard as our April 2025…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 294,165 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 232,968 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans