req.readyState sticking as 1 when Calling ACtion

Oct 11, 2016 at 10:12 AM
Hi there,

I seem to be having issues where the req.readyState returns 1 and therefore calls the error callback, even when the Action is being triggered correctly.

Is there something I could be doing wrong that would be causing this? I've found that clearing the client cache will fix the issue for 1 attempt, before it then breaks again.

Cheers!
Coordinator
Dec 9, 2016 at 9:08 PM
Hi, the success or error callback should only ever fire when the readyState is 4. The thing that determines success or error is the req.status (200 = success).

The onreadystatechange event is triggered five times (0-4), one time for each change in readyState.

Regards
Paul
Dec 21, 2016 at 2:54 PM
I have a workflow which cannot be activated. Because if I activate it it will fire automatically when ever it matches the criteria. Is the workflow should be activated before? or it can even call a workflow in Draft status?
Coordinator
Feb 26 at 9:14 PM
processjs can only call actions, workflows, and dialogs if they're activated.