What this solves
This procedure gives an operator one controlled path to connect storage, upload a test asset and prove that downstream modules can read it.
When to use it
Use it during initial setup, a planned change or incident recovery when you need to connect storage, upload a test asset and prove that downstream modules can read it.
Dashboard path
/storages/list/files/listPrerequisites
Administrator access to the Callaba instance and permission to change this module.
A maintenance window or a non-production resource plus a real test source or client.
A record of the current values, allocated ports and credentials before you save changes.
Steps in the Callaba UI
- 01
In the dashboard sidebar, follow Quick start → Storages. Open the source-backed route /storages/list. In the dashboard sidebar, follow Quick start → File manager. Open the source-backed route /files/list.
- 02
Before changing File manager and storage operations, record these current values: storage_type, file_path, file_name, storage_id.
- 03
In File manager and storage operations, set storage_type, file_path, file_name, storage_id so you can connect storage, upload a test asset and prove that downstream modules can read it. Keep unrelated values unchanged.
- 04
Run Save [creating-form-save] → Import [import-button]. Wait for the form or listing to settle before testing another variable.
- 05
Use a real source, destination or browser client and confirm these live signals: file_loading, progress, files, storage_type.
storage_typefile_pathfile_namestorage_id
- Save
creating-form-save - Import
import-button
file_loadingprogressfilesstorage_type
Expected result
The runbook is complete when Save [creating-form-save] → Import [import-button] succeeds and a real workflow reports file_loading, progress, files, storage_type.
Troubleshooting
The saved change does not appear
Confirm the save response, refresh the module once and compare the visible values with the record made before the change. Correct validation errors before retrying.
The connection or playback path fails
Check the exact host, port, protocol, credentials and firewall path used by the real client. Test one source and one destination before restoring the full workflow.
The module starts but health is unstable
Return to the last known working values, inspect live statistics and process errors, then reintroduce one change at a time.
Product page / Exact API reference
Continue with the commercial product context or automate the same operation from its verified API endpoint.