Why do I get a '409 Conflict' error when dealing with an agent session?
When you attempt to start a session for a user that already has an active session, or end a session that has already been ended, the API will return an error code (409 Conflict).
When I join an existing session, will I get the same sessionId?
No. When any device or application joins running session it receives a unique identifier for that session.
What will happen if a session which has other joined applications ends?
All events for a running session are available to every joined application or client so the session would end for all connected applications.
How can I make sure that my request to change a system resource state was completed?
All state changes will trigger an event to indicate that the state has been changed. See the Using events
tutorial to learn more about how events can be used.
Why do I get a different sessionId every time I get each new event?
Your sessionId contains a timestamp that tells the system the last time you got events. This is used to keep the platform and client applications in sync.