User Q&A - Recent Threads

Question: Verify FieldPulse mobile sync after offline work

FieldPulse Community Manager — Thu, 09 Jul 2026 19:02:24 GMT

When a technician completes a work order while offline and then reconnects, what checks should the dispatcher use to confirm the status update and notes synced correctly in FieldPulse?

Confirmed working: Offline status update sync resolved

Sam Kowalski — Wed, 22 Apr 2026 11:30:00 GMT

hey all just wanted to drop back in on that offline status update thread — the thing josh suggested actually works lol

so i was in a dead zone yesterday, updated like 4 jobs to "completed" while i was out there, got back to wifi range and boom they all synced up clean. no duplicates, no weird states, just worked

for anyone who missed it: basically just make sure you actually hit the status dropdown and select completed, don't just type notes and assume it saves. the app queues it proper if you do it through the status flow

anyway figured i'd confirm since i was skeptical ngl. working offline in fieldpulse is actually legit now

RE: Confirmed working: Offline status update sync resolved

FieldPulse Community Manager — Thu, 09 Jul 2026 18:43:34 GMT

Thanks for sharing this. For FieldPulse, I would first confirm that the mobile app has synced recently, then compare the work order status in the technician view with what dispatch sees. If those match, capturing the job number and last sync time will make it easier for support to trace the update.

RE: Confirmed working: Offline status update sync resolved

Priya Nair (Staff) — Thu, 23 Apr 2026 09:17:00 GMT

Hi Sam, happy to help confirm this!

What you're describing is exactly how offline status updates are designed to work. Here's what's happening under the hood:

Status changes made offline are stored in a local queue
On reconnect, the app syncs automatically (you'll see the spinner Sam mentioned)
Conflicts are resolved server-side with timestamps

Important: Do not force-close the app while offline, as Art and Josh noted — this clears the queue. Backgrounding the app is fine.

We've also seen improved reliability with this flow in app version 3.2.1 and later. If anyone is still experiencing issues after following these steps, feel free to tag me and I can dig into your specific account.

RE: Confirmed working: Offline status update sync resolved

Art Kowalczyk — Wed, 22 Apr 2026 18:05:00 GMT

see told ya. happened to me twice before i figured it out

RE: Confirmed working: Offline status update sync resolved

Josh Mercer — Wed, 22 Apr 2026 17:23:00 GMT

Pro tip: Art's right about that one — the queue lives in memory, so if you swipe away the app while offline those pending changes can get lost. I've trained my guys to just let the app sleep in background if they're in a dead zone.

Sam, glad it worked out for you. For anyone else reading, the full walkthrough is in this Help Center article on syncing when you reconnect.

RE: Confirmed working: Offline status update sync resolved

Art Kowalczyk — Wed, 22 Apr 2026 16:08:00 GMT

in my experience this only works if you don't force close the app. kill it while offline and you're hosed

RE: Confirmed working: Offline status update sync resolved

Sam Kowalski — Wed, 22 Apr 2026 14:12:00 GMT

nah just opened the app on wifi and let it sit for like 30 seconds. saw the little sync spinner do its thing and all my jobs updated. didn't have to hit any buttons or anything

RE: Confirmed working: Offline status update sync resolved

Tyler Hatch — Wed, 22 Apr 2026 13:45:00 GMT

oh nice thanks for confirming this sam i was wondering if it actually worked. did u do anything special on reconnect or did it just auto sync

RE: QuickBooks integration disconnecting daily — authentication issue?

Priya Nair (Staff) — Tue, 21 Apr 2026 09:45:00 GMT

Hi Brandon — the re-authentication with PKCE (steps above) should be a one-time fix, not an ongoing requirement. Once you've reconnected under the new OAuth flow, the tokens should refresh automatically without daily expiration.

If you're still seeing daily disconnects after completing those steps, that's a bug we need to investigate immediately. Please open a ticket with your account ID and we'll escalate to engineering same-day.

QuickBooks integration disconnecting daily — authentication issue?

Fatima Al-Rashid — Sun, 19 Apr 2026 16:15:00 GMT

From a governance perspective, we require stable integration connectivity for our financial audit trail. Since Thursday of last week, our QuickBooks Online connection has been terminating every 24 hours, necessitating manual re-authentication by an administrator with appropriate credentials.

It is worth noting that:

No configuration changes were made to either FieldPulse or QuickBooks Online prior to this behavior commencing
The disconnection occurs consistently at approximately 4:00 PM UTC daily
Our API usage has remained within documented rate limits
Refresh token rotation appears to be failing silently — no error notifications are generated

I have confirmed that our QuickBooks Online subscription is active and that third-party app permissions remain granted. The re-authentication flow completes successfully each time, suggesting the OAuth consent is not being revoked at the source.

Is this a known issue with the QuickBooks integration connector? We are evaluating whether to implement a manual token refresh workflow via API, but this would introduce operational overhead we had not anticipated.

Our current environment: FieldPulse 3.3.1, QuickBooks Online Plus, SSO not enabled for the integration account.

RE: QuickBooks integration disconnecting daily — authentication issue?

Brandon Okafor — Tue, 21 Apr 2026 08:12:00 GMT

We've been dealing with this too — my team can't invoice properly when the sync drops. Is there a timeline for a permanent fix, or is re-authentication now a weekly task?

We need this working reliably for month-end close.

RE: QuickBooks integration disconnecting daily — authentication issue?

Fatima Al-Rashid — Mon, 20 Apr 2026 16:02:00 GMT

It is worth noting that we do maintain a separate data extraction process that leverages the FieldPulse API, not direct QuickBooks API access. However, I will verify with our development team whether any direct token usage exists that I am not aware of.

From a governance perspective, we prefer to avoid token extraction entirely and use dedicated service accounts where possible.

RE: QuickBooks integration disconnecting daily — authentication issue?

Mike Dolan — Mon, 20 Apr 2026 14:33:00 GMT

Same thing happened to us last month. Reconnecting with PKCE fixed it.

One thing — if you have any scheduled reports or automated syncs, they'll fail during the 2-3 minute window Priya mentioned. We learned that the hard way with our nightly invoice push.

RE: QuickBooks integration disconnecting daily — authentication issue?

Devon Marsh — Mon, 20 Apr 2026 10:45:00 GMT

Heads up — if you're running any custom scripts that hit the QBO API directly using tokens extracted from FieldPulse, those will definitely break with the PKCE migration. The token format changes slightly.

YMMV, but we had to update our internal reporting tool that was piggybacking on the FieldPulse OAuth flow. Worth checking if your team has anything similar.

RE: QuickBooks integration disconnecting daily — authentication issue?

Priya Nair (Staff) — Mon, 20 Apr 2026 09:17:00 GMT

Hi Fatima — happy to help clarify this! Daniel's guidance above is solid, and I want to add that we're tracking a specific issue with QuickBooks refresh token persistence that may be affecting your connection.

Here's what's happening: QuickBooks Online recently tightened their OAuth 2.0 implementation to require PKCE (Proof Key for Code Exchange) on all new connections. FieldPulse has supported this since version 3.2, but connections established before that may be experiencing the exact 24-hour expiration pattern you're describing. The existing tokens are grandfathered, but the refresh flow is being rejected by Intuit's servers.

To resolve this, you'll need to reauthorize the connection using our updated OAuth flow. Here's the step-by-step:

Navigate to Settings > Integrations > QuickBooks
Click Disconnect (do not skip this — the old token must be fully invalidated)
Wait 2-3 minutes for the token to clear from our cache
Click Connect to QuickBooks
Sign in with your QuickBooks credentials when prompted
On the authorization screen, verify you see 'This app uses industry-standard encryption' — this confirms PKCE is active

This issue is documented in QuickBooks Sync Duplicating Invoice Line Items — while the symptoms differ, the root cause (token handling) is related.

If you complete these steps and still see daily disconnections, please open a support ticket and reference this thread. We can escalate to our integrations team for deeper token flow analysis.

RE: QuickBooks integration disconnecting daily — authentication issue?

Fatima Al-Rashid — Sun, 19 Apr 2026 19:28:00 GMT

It is worth noting that we do not have direct API access to integration status endpoints — this is managed through the FieldPulse web interface. The integration panel displays 'Connection expired' with a timestamp matching approximately 24 hours from the previous authorization.

I have requested our development team to inspect network traffic during the next scheduled disconnection, which should occur tomorrow at 4:00 PM UTC.

RE: QuickBooks integration disconnecting daily — authentication issue?

Carlos Vega — Sun, 19 Apr 2026 18:05:00 GMT

Can you share the full response from GET /api/v1/integrations/quickbooks/status when the connection shows as disconnected? Specifically need last_error and token_expires_at.

Also helpful: are you seeing 401 responses in your network logs, or is the disconnect happening before any API call is attempted?

RE: QuickBooks integration disconnecting daily — authentication issue?

Daniel Cho (Staff) — Sun, 19 Apr 2026 17:42:00 GMT

Hi Fatima — in my experience, this pattern typically points to a mismatch between how FieldPulse is requesting token refresh and a recent change on Intuit's side regarding refresh token lifetimes. What I typically recommend is verifying a few specific items before assuming it's a bug on either platform.

QuickBooks Online made a change in early 2024 that reduced refresh token validity for certain connection types when the app is in 'development' mode versus 'production' mode. However, that shouldn't apply to established FieldPulse connections. More likely, what we're seeing here is that the token refresh is happening at the 24-hour mark, but something in the token storage is not persisting the new refresh token that's returned with the access token.

Here's what I would check:

First, look at whether your integration was originally set up under a different QuickBooks user account that may have since been deactivated or had its permissions modified. The FieldPulse integration stores credentials against the specific QBO user who authorized it, not just the company. If that user leaves or their role changes, the refresh can fail even though the initial connection test passes.

Second, there's a known interaction between certain firewall configurations and the token endpoint that can cause the response containing the new refresh token to be dropped. This is rare but I've seen it twice in enterprise environments with strict outbound filtering.

Third, and this is the most common cause in my experience, QuickBooks Online will invalidate refresh tokens if the same user authorizes the app multiple times across different browsers or devices. The most recent authorization wins, and previous refresh tokens become invalid. If someone on your team has been testing or re-authenticating, that would explain the 24-hour cycle.

What I typically recommend as a next step: disconnect the integration entirely from FieldPulse, then revoke the app authorization from within QuickBooks Online (Settings > Apps > FieldPulse > Disconnect), wait approximately 10 minutes, and reconnect using a dedicated service account rather than a personal user account. This ensures no other sessions can interfere with the token lifecycle.

From a governance perspective, this also aligns better with audit requirements since the service account can be configured with minimal permissions and monitored separately.

RE: User invite emails not delivering — spam folder checked

Ray DeLuca — Mon, 13 Apr 2026 15:30:00 GMT

same thing happened to us last month... email just stopped working for 3 days, then fixed itself

we never got an explanation. might want to ask for root cause on your ticket so it doesn't happen again during your rollout

User invite emails not delivering — spam folder checked

Anita Sharma — Mon, 13 Apr 2026 10:50:00 GMT

I have confirmed that user invitation emails are not being delivered to recipients' inboxes. I have verified the following:

The email addresses are valid and properly formatted
Recipients have checked spam/junk folders — no emails present
Our corporate mail gateway shows no rejected or quarantined messages from FieldPulse
Invitations sent to addresses within our domain and external domains (Gmail, Outlook 365) are equally affected

This issue began on 2026-04-11. Prior to this date, invitations were delivered successfully. I can reproduce this consistently across multiple attempts.

Our organization has 47 pending invites that must be sent before the end of this week. I require either a resolution or a manual workaround to generate invitation links directly.

Account ID: FP-ENT-2847-8812

Please advise on next steps.

RE: User invite emails not delivering — spam folder checked

Anita Sharma — Mon, 13 Apr 2026 14:12:00 GMT

I have confirmed that the bulk resend option appears after selecting at least one user. I have successfully resent all 47 pending invitations.

47/47 delivered successfully as verified by recipient confirmation.

I will note this UI pattern for our internal documentation. Thank you for the rapid resolution.

RE: User invite emails not delivering — spam folder checked

Eli Torres (Staff) — Mon, 13 Apr 2026 13:40:00 GMT

yeah this one tripped me up too when I first looked at it — the bulk action is actually hidden unless you select at least one user

try this:

go to pending invites
check the box next to one user (anyone)
a toolbar appears at the top with 'Resend' and 'Delete' options
now check the master checkbox in the header row to select all 47
hit Resend

the UX isn't great here, we should probably surface those actions always-visible. I've flagged it with the design team.

if that doesn't work for some reason, I can generate the invites via API and send you a CSV with direct invitation links — just ping me here

RE: User invite emails not delivering — spam folder checked

Anita Sharma — Mon, 13 Apr 2026 12:05:00 GMT

I have confirmed that a test invitation sent at 12:02 UTC was delivered successfully to both internal and external recipients.

However, when I navigate to Settings > Team Members > Pending Invites, I do not see a bulk resend option. I can only resend individually, which is not operationally feasible for 47 pending invitations.

Please provide the bulk resend procedure or escalate for API-based generation of invitation links.

RE: User invite emails not delivering — spam folder checked

Priya Nair (Staff) — Mon, 13 Apr 2026 11:23:00 GMT

Hi Anita, happy to help investigate this with you!

I have checked our email delivery logs for your account and I do see a spike in soft bounces starting April 11th. It appears our primary sending domain was temporarily flagged by one major provider. Our operations team rotated to a secondary sending domain at 09:15 UTC today.

Can you please attempt one new invitation and confirm receipt? If successful, I will provide instructions for resending the 47 pending invites in bulk.

Settings > Team Members > Pending Invites > Resend

Please let me know the results and I will proceed accordingly.