Hi Robert, Once you save the Session, the saved nodes should be visible to other Sessions. Is your job processor using a long-lived session? If so, try calling refresh on the Session. This is especially true if you are using some kind of clustering.
Regards, Justin On Jul 22, 2012 1:14 PM, "Robert A. Decker" <[email protected]> wrote: > Hi, > > I create a node and save it, then fire off an event that starts a process > that begins updating the node. > > However, there are times when the node hasn't been written by the first > save yet, and so my job processor has nothing to work on. > > Is the correct strategy to have the job processor wait a few milliseconds > and try again? and again and again…? > > > Rob
