Skip to main content
Solved

User Interaction workflow Client error: Cannot read properties of null (reading 'response') during ContinueWorkflow request

  • April 13, 2026
  • 2 replies
  • 36 views

Forum|alt.badge.img+1

I’ve created a User Interaction workflow that triggers after adding or editing an expense detail line. It will ask the user for an input and updates a custom field on that line. As a user, I get a client error yet the workflow is triggered successfully but as IFSAPP, I don’t. I thought it was a permission issue but my user has full access to all the projections used in the workflow.

 

If I’m logged into IFSAPP and add/edit an expense detail line:

  1. The workflow is triggered and asks for a value to update the custom field.
  2. The custom field gets updated.
  3. No error.

If I’m logged in as a user and add/edit an expense detail line:

  1. The workflow is triggered and asks for a value to update a custom field.
  2. I receive a Client error.
  3. I refresh the page and the custom field has been updated.

I’ve watched the workflow and captured the payload that received the Client error to use for debugging. I used that payload to troubleshoot in the workflow design but it went through successfully so I don’t see any issues in the workflow itself.

 

Using Developer Tools in the browser, the Client error occurs in the middle of the request

………. /main/ifsapplications/projection/v1/WorkflowService.svc/ContinueWorkflow………...“

The actual client error message, that only comes up as a signed in user, displays:

Url (parameters included) = ……main/ifsapplications/web/page/TravelExpensesEmployee/MyExpenseDetailPage;$filter=CompanyId..................

Error stack:

Cannot read properties of null (reading 'response')

TypeError: Cannot read properties of null (reading 'response')…..

 

The user has full access to the TravelExpensesEmployeeHandling projection and MyExpenseDetailPage page.

Any ideas of what is causing this issue?

Best answer by wahelk

is the end user has access as external or full for workflow. probably data level restriction on accessing expenses.

2 replies

wahelk
Hero (Former Employee)
Forum|alt.badge.img+11
  • Hero (Former Employee)
  • Answer
  • April 14, 2026

is the end user has access as external or full for workflow. probably data level restriction on accessing expenses.


Forum|alt.badge.img+1
  • Author
  • Do Gooder (Partner)
  • April 14, 2026

is the end user has access as external or full for workflow. probably data level restriction on accessing expenses.

Hi ​@wahelk, thanks for the response! I was missing giving them full access to the workflow.

However, when I tried it while being in incognito mode - it worked without getting the Client error. When I used a normal browser (after I cleared my cache) - I still got the Client error.

 

I also turned off the workflow and added expense lines as the user without any issues so I’m not sure if it’s data level restrictions.

UPDATE: I’m not sure what happened when I tested it out after I cleared my cache the first time but I cleared it again and now it works. It looks like the solution was to give the user’s permission set access to the workflow.