Actions101
- š¤ Chatting Actions
- š„ļø Sessions Actions
- š Auth Actions
- š¼ļø Screenshot Actions
- š¢ Channels Actions
- š¢ Status Actions
- š¬ Chats Actions
- š¤ Contacts Actions
- š„ Groups Actions
- ā Presence Actions
- š·ļø Labels Actions
- š Observability Actions
Overview
This node is designed to restart a session in a system that manages sessions. It is useful in scenarios where a session needs to be refreshed or reset, such as recovering from errors, applying new configurations, or restarting a workflow associated with a session. For example, if a session becomes unresponsive or encounters an error, this node can be used to programmatically restart it to restore normal operation.
Use Case Examples
- Restarting a user session in a web application to apply new settings.
- Resetting a session in an automation workflow to recover from an error state.
Properties
| Name | Meaning |
|---|---|
| Session | The name of the session to be restarted. This is a required string input that identifies which session the operation will target. |
| Request Options | Optional settings to control the HTTP request behavior, including batching, SSL certificate validation, proxy usage, and timeout settings. |
Output
JSON
session- The name of the session that was restarted.status- The status or result of the restart operation, indicating success or failure.message- Additional information or error messages related to the restart operation.
Dependencies
- Requires an API key credential or authentication token to access the session management system's API.
Troubleshooting
- Common issues include providing an invalid or non-existent session name, which results in errors indicating the session could not be found.
- Timeout errors may occur if the server does not respond within the specified timeout period; increasing the timeout or checking network connectivity can help.
- SSL certificate validation errors can be bypassed by enabling the 'Ignore SSL Issues' option, but this should be used with caution due to security risks.