Receiving 403 on all OR v1.1 to /results intermittently.

Daniel Baumgartner
Daniel Baumgartner
Name Dropper Participant Facilitator 1
in Blackbaud K–12 Education Solutions™ General Discussions

Our OneRoster v1.1 connection is failing when attempting to PUT or PATCH to the /results endpoint with a 403 intermittently.
We were previously running 3 times a day without issue, and it started failing on all lineitem and results with 403. We decided to change to running once a day on the off chance that it's a speed issue (normally a 429), and it initially worked on the next sync, but then failed on results the following sync.

The only things that we can think of that would be causing this are the general causes of a 403, but the customer is adamant that they've not made any changes.

Any thoughts are welcome.

Tagged:

Comments

  • Todd DeSchuiteneer
    Todd DeSchuiteneer Blackbaud Employee
    Tenth Anniversary Kudos 3 Name Dropper Participant

    Hi @Daniel Baumgartner , Could you post the full error message you are receiving and confirm lineitems were inserted using the PUT LineItem OneRoster endpoint?

  • Daniel Baumgartner
    Daniel Baumgartner
    Name Dropper Participant Facilitator 1

    @Todd DeSchuiteneer
    This is the full response we're getting:
    {"statusInfoSet":[{"imsx_codeMajor":"failure","imsx_severity":"error"}]}

    Yes, I can confirm we're using the PUT LineItem OR endpoint.

  • Todd DeSchuiteneer
    Todd DeSchuiteneer Blackbaud Employee
    Tenth Anniversary Kudos 3 Name Dropper Participant

    Thank you @Daniel Baumgartner. I have been trying to reproduce this issue and I have been unsuccessful. Is the issue only happening with one school? Can you tell me if the calls that fail are ever succeeding after retrying?

  • Daniel Baumgartner
    Daniel Baumgartner
    Name Dropper Participant Facilitator 1

    @Todd DeSchuiteneer
    {"statusInfoSet":[{"imsx_codeMajor":"failure","imsx_severity":"error"}]} IS the full error message.
    Yes, I can confirm that the lineitems were inserted using the PUT LineItem OneRoster endpoint.

    This was all working up until last week. Everything that we're seeing and know is pointing to a change that was made to our customers system, but they are adamant that they did not make any changes.

Categories