Errors, limitations and troubleshooting

Service Journeys

Resolve an inactive module route

Activate the module; controllers return not found when the module is inactive.

Resolve staff access errors

Grant View/Create/Edit as needed.

Resolve create validation errors

Check required type/title/client, valid optional email, maximum lengths and exact dates.

Resolve invalid status/progress

Choose an installed status and progress 0–100.

Resolve stage sequence errors

Complete stages in order.

Resolve missing compliance manager

Select an active manager for stage 2.

Resolve portal visibility

Link the correct customer/contact; clients cannot see unowned journeys.

Resolve missing activity fields

Provide both label and description.

Resolve missing task title

Provide the required title.

Resolve blank message

Enter message content.

Resolve document upload errors

Provide type, supported file/MIME and stay within 10 MB.

Resolve document not found

Check ownership, visible_to_client and record/file content.

Resolve failed notifications

Check recipient, SMTP, sender options, logs and retry timing.

Resolve missing reminders

Confirm CRM cron executes before_cron_run and the module is active.

Resolve unexpected outstanding badge

Only completed_successfully clears the count.

Understand API limitations

The module itself has no standalone API controller; supported portal integration is provided by the separate Proplix Secure API Gateway where installed.

Understand webhook limitations

No outbound webhook manager is supplied.

Understand deletion limitations

No record deletion interface/capability is supplied.

Run production verification

Test each type, public intake, all statuses, six stages, client visibility, documents and notification retries.