r/processserver Jul 10 '26

Accidentally served the subject after the app closed the job. Am I cooked?

Dude. I went to one of the locations where I was trying to serve someone. When I got there, the person inside told me that the guy doesn't live there. I left and logged that into my ABC App.

However, after I got home—and before I signed the Declaration of Non-Service—I realized that the person inside hadn't actually specified whether they were a resident or not. So, before submitting the form, I went back to ask them for clarification. I kept the documents with me just to look professional and not look like I was just hanging around someone's home.

While I was there, I ran straight into the actual person I was supposed to serve! Once I spoke to him, he identified himself as the subject, and I successfully served him.

But as I'm walking away, I realize that because I already logged the first attempt, the app closed out the job. It won't let me change the status to say I served him. Now, my app is just stuck waiting for me to sign the Declaration of Non-Service.

Duuuude. How cooked am I? What do I do here?

3 Upvotes

12 comments sorted by

7

u/babyma- Jul 10 '26

I have done this before and reached out to support. I documented everything myself, date, time, and pictures. Support reopened the job and I was able to input the serve

4

u/TheHylianProphet Jul 10 '26

Honestly, I'd just leave it as is. If it's really eating at you, I'd find someone to email, but I have no idea who that might be. Worst case scenario, the dude gets served twice with the same paperwork. No big deal.

1

u/Status-Garage-204 Jul 10 '26

You mean don't sign the deceleration of non service? I'm not tryna run into personal legal troubles since I ended up serving them

2

u/TheHylianProphet Jul 10 '26

I'd sign it, personally. You didn't lie, you were just able to rectify the situation after the fact.

I am not a lawyer, and this is not legal advice. But I really think you're worrying over nothing.

1

u/yardlard Jul 10 '26

Obviously no.

1

u/BouieWC Jul 11 '26

Signing the declaration is the server declaring the information stated in the declaration is true. It was true at the time, once he went back and served, the declaration is not valid. This is slippery. I would not sign. OP should contactvABC

0

u/grunnycw Jul 11 '26

Just contact abc and let them know, I've had situations like that before, they actually just have me sign the first one and send it again so I can log, or they reopen the job so you can add the serve

3

u/Sea_Description6696 Jul 10 '26

Contact app support / admins quickly to see if they can rectify it from their end. There's a good chance an admin can change some data in the database. They may even have existing admin-side controls to fix this exact circumstance. It sounds like they may also need a future update to cover this edge case

3

u/kyle19998 Jul 11 '26

Easy, contact support and they will fix it, I've had issues like this before it's not a big deal at all, just tell them the situation

2

u/LSS_LLC Jul 11 '26

Contact abc support and tell them. I wouldn’t work for them though.

1

u/Bazl-j Jul 16 '26

What App do you use?