Documentation
Troubleshooting starts with the invoice record, not guesswork.
Most ChaseNow issues can be narrowed quickly by checking invoice state, due date, event history, and whether the chase is active or paused.
Steps
How to handle troubleshooting in ChaseNow
Open the invoice record first and verify the status.
Check the due date and next scheduled milestone in the timeline.
Review the event log to confirm whether a message was already sent.
If the invoice is paused or marked paid, resume or reopen it only if that matches reality.
Use the in-app contact flow with the invoice reference number if the problem still persists.
Troubleshooting path
Status, timeline, and event log usually reveal the issue
Notes
Operational notes
Many apparent scheduling issues are really status issues caused by paused or already resolved invoices.
The timeline should always be interpreted relative to the invoice due date.
When reporting a bug, the invoice reference number is the fastest way to help support investigate.
FAQ
Why does my timeline not show the reminder I expected?
The schedule may have skipped that checkpoint because the invoice entered the system too close to the due date or because the current status is paused or resolved.
What should I include when I contact support?
Include the invoice reference number, what you expected to happen, and what the event log currently shows.
Related pages
Next step
Use the docs, then put the workflow to work.
The goal of the documentation is not to describe software in the abstract. It is to help you get an invoice into ChaseNow and keep the follow-up moving.