Connections & workflows
Investigate missing or delayed information
Trace one record from the responsible source to the destination before assuming a report or workflow is wrong.
Start with one record and a time
A missing value can reflect a different period, an incomplete source record, a delayed handoff, a rejected update or an access restriction. Following one redacted example helps narrow the cause without changing several systems at once.
- Confirm the expected record in its responsible source system.
- Note its identifier, status and relevant time zone.
- Check the destination and the last known handoff or verification result.
- A dashboard refresh cannot supply information that the source or connection has not provided.
- Avoid creating duplicate records to make a missing item appear.
Compare the right things
Use the same environment, identifier, status definition and reporting period. A test record and a live record, or an order date and a payment date, can produce different views without indicating a lost transaction.
- Source and destination identifiers.
- The field expected to change and the accepted mapping.
- Any visible rejection, permission or provider error.
Send a reproducible example
Use an authorized private support channel for business references. Redact personal details and credentials from screenshots and logs.
- What you expected and what actually appeared.
- The source, destination, environment and time of the example.
- The last successful result or a similar record that works.
Need help with your workspace?
Open a private support request with the steps, expected result and business impact. Leave out passwords, API keys and payment details.
Open client support