Workday integration error: response_size_exceeded

Comments

4 comments

  • Geoff Tipley
    Engaged
    Awesome Follow-up

    I might be getting a false positive from Celigo on the connection test in the first place

    0
  • Tyler Lamparter Principal Product Manager
    Awesome Follow-up
    Engaged
    Top Contributor
    Answer Pro
    Celigo University Level 4: Legendary

    Geoff Tipley if you think it may be connection test prior to export preview even running, you can remove everything from the test section and see if you get the same result.

     

    For your export, do you have a path to records specified? If not, then the single response may be too large to fit on a page. Your path should be set to where individual records can be found within the response.

    0
  • Brijal Tailor

    Geoff Tipley Were you able to resolve this error? If So How? I am getting same error during test sync.

    0
  • Geoff Tipley
    Engaged
    Awesome Follow-up

    Brijal Tailor yes! I figured out that it just tries to return all of the records at once: the standard Workday connector lacks a per-page limit. If you edit the standard connector and switch the mode from Simple to HTTP, it'll let you edit the HTTP request body. Look for the </bscv:Page> closing tag and add after that:

    <bscv:Count>{{export.pageSize}}</bscv:Count>

    and that should allow the pageSize field value to restrict the results per page. You could even use handlebars to have it use the previewPanelRecords value when that available. (Edit export > Preview data)

    0

Please sign in to leave a comment.