Resolve a concurrent Bilty draft edit conflict
Reload the latest draft when the version or editing lock shows that another session changed the record. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries.
What you’ll accomplish
Reload the latest draft when the version or editing lock shows that another session changed the record. Bilty Management keeps drafts, issued records, public capability links, finance, integration events and audit evidence as connected but separately verifiable records.
How the workflow fits together
Create a Bilty through the three-step form, autosave safely, resolve missing information and recover drafts. Use the module's current status, permission checks, warnings and linked records to decide the next supported action. Where a downstream invoice, WhatsApp queue item, webhook, PDF, POD record or audit event applies, verify it separately.
Follow these steps
- Go to Bilty Management → Drafts / Dashboard and reproduce the issue on the intended tenant and record.
- Read the exact warning, validation response, lock state, integration diagnostic or status before changing anything.
- Check the inputs and dependency relevant to this problem: Reload the latest draft when the version or editing lock shows that another session changed the record.
- Correct the smallest supported cause; do not bypass permissions, protected validation or security controls.
- Retry once, then reopen the record and confirm the stored state and audit evidence.
Fields and decisions to review
Record, audit and evidence checks
Reopen the relevant Bilty record or register and confirm its identifier, current status, related parties, timestamps and connected evidence. Check the audit/compliance, payment, public-link, report, API, webhook or WhatsApp evidence that applies to this workflow rather than relying only on a success alert.
How to confirm it worked
Return to Bilty Management → Drafts / Dashboard or the resulting register and verify that the stored state matches the intended action. For any downstream automation, confirm the downstream record or queue/log entry as a separate completion check.
Technical basis for this guidance
This guide was checked against controllers/Bilty_management.php; models/Bilty_management_model.php; views/admin/dashboard.php; assets/js/dashboard.js. It documents only behaviour exposed or enforced by the supplied module; internal secrets, raw signature payloads and unsupported future workflow assumptions are intentionally excluded.
Controls, checks and common mistakes
- Work only on the intended tenant and Bilty record.
- Do not bypass a missing permission, validation blocker or protected status by changing unrelated settings.
- Verify the stored record, downstream integration state and audit evidence after any material action.