Calling API issue

I know it’s simple that I’m missing but I am having trouble getting my app to call API workflows I have created. I even created a very simple one where I call the API (with no conditions) to make a change in a User parameter called ‘test field’(yes/no)

I will attach screenshots. Please let me know if I should provide any other information to help resolve this issue …

*I have the personal level account plan

  • I have the “This app exposes a Workflow API & This app exposes a Data API” boxes checked

Just to reiterate, I’m unable to get any of my API workflows to be called. This was not an issue last week, so I suspect I clumsily clicked something that created this situation. Any assistance would be greatly appreciated.

Regards

Thanks for the screenshots, but it’s helpful to have an unobstructed view of the steps in the workflow. (Ex. Step 2 could be “terminate this workflow” or “log the user out”) :stuck_out_tongue:

A few minor things to check:

  • Have you implemented any privacy roles in your app that could potentially conflict? (Try ticking the “Ignore privacy rules when running the workflow” box to see if you have any change.
  • Double check to ensure you haven’t “Paused” workflows in the scheduled workflows tab.

Here you go …

I clicked on the “Ignore privacy …” box also I ran it in debugger.

I checked out the server logs and it shows the API being called so I guess being called is not the issue, but the action does not seem to be executed. In the simple API call I created I pass the current user into the API workflow and make a parameter from ‘test field = no’ to ‘test field = yes’

1 Like

Feel free to PM me a link to your editor and I’ll take a look.

From the screen shots you shared, it looks like you have two API workflows being scheduled in this workflow. Just to double check, might these conflict with each other in some way? (Your screenshots are a bit too closely cropped (ie. Step 4 and Step 5 isn’t visible) - sometimes it’s the surrounding information that provides good clues).

Let’s see your step that changes the field. It kinda sounds like your sever side workflow is getting executed, it’s just you’ve got a bug in the step that’s making you THINK nothing is happening, right?

Btw, if you want to invert a Boolean, set:

Boolean-thing = Boolean-thing is “no”

(This flip flops yes to no and no to yes.)

Oh, the other thing: are you SURE you’re passing the right user? And are u SURE you’re checking the right user’s Boolean value u think isn’t being set?

My questions in a nutshell are: How do you KNOW your server side workflow isn’t working as programmed? It sounds like you are not sure of that…

Maybe revert (restore) to version control from 7 days ago. If it works, easier to find the bug. You can then restore from days 6,5,4… until the bug appears again. Once found, you can restore to the actual date and fix it.

3 Likes