Runbook: Sensedia Integrations — Undeploy an integration
| Field | Value |
|---|---|
| System | Sensedia Integrations |
| Procedure | Undeploy (rollback) an integration flow |
| Owner | IT Production |
| Estimated time | 15–20 minutes |
| Maintenance window required? | No |
| Approval required? | Yes — per change management process |
Pre-conditions
Before running this runbook, verify:
- Active username and password on the Sensedia platform.
- Access to the Patria tenant with deploy permissions in Production.
- The exact name of the integration flow to revert has been confirmed.
- An active deployment exists in Production for the specified flow.
Rollback plan
This runbook is the rollback procedure. There is no automatic reversion of an undeploy. If the flow needs to be redeployed after the undeploy, run the corresponding deploy runbook.
Procedure
Step 1 — Log in to the platform
Open a browser and navigate to:
https://platform-production.sensedia.com/ipaas/
If prompted for login, go to:
https://signin.platform-production.sensedia.com/tenant-signin
In the Tenant Alias field, enter Patria and click Go to your account.
Enter your username and password, then confirm the login.
Expected result: The Sensedia platform loads successfully.
Step 2 — Navigate to Deployments
In the left-hand menu, click Deployments.
Expected result: The list of active deployments is displayed.
Step 3 — Filter by Production environment
In the environment filter, select Production.
In the search box, enter the name of the integration flow to revert and click SEARCH.
Expected result: The deployment for the specified flow is displayed.
Step 4 — Verify deployment identity
Warning
Critical step — do not skip: Before proceeding, verify that the Integration Flow column shows exactly the name of the flow to revert. Do not proceed if there is any doubt about the identity of the deployment.
Visually confirm:
- The integration flow name matches exactly the flow being targeted.
- The environment is
Production.
Expected result: The deployment is confirmed to correspond to the correct flow.
Step 5 — Execute the undeploy
- Click the vertical three-dot menu (⋮) on the right side of the deployment row.
- Select Undeploy.
- Confirm the action in the confirmation dialog.
Expected result: The deployment disappears from the list or changes to a status other than DEPLOYED.
Step 6 — Final verification
- The integration flow no longer appears as
DEPLOYEDin Production. - If the flow was replacing an existing process on another platform (e.g., Pentaho), reactivate the schedule on that platform.
- Notify the functional team that the flow was reverted.
- Record the incident with date, time, and a description of the error that triggered the rollback.
Troubleshooting
| Error / Symptom | Likely cause | Solution |
|---|---|---|
| Deployment not found in the list | The flow is not deployed in Production | Verify the selected environment filter; confirm with the team that it was deployed |
| ”Undeploy” option not available | Insufficient permissions on the tenant | Request deploy/undeploy permissions in Production via ServiceNow |
Deployment returns to DEPLOYED status | The flow’s scheduler automatically redeployed it | Disable the flow’s scheduler before performing the undeploy |
| Authentication error on the platform | Expired credentials or revoked access | Request a credential reset or access renewal via ServiceNow |
References
- Deploy runbook: runbook-deploy.md
- Log review runbook: runbook-check-logs.md
- System documentation:
06-systems/sensedia/index.md