I don’t believe I had an issue when I first wrote my module, but it became apparent with a recent update. It was kinda a comedy of errors. First the background services weren’t running so claims weren’t being sent and now that I have it running again, I think I have a race condition on what wants to send the claim file.
My module uses REST to send the file not SFTP, so what I’m seeing now are that people are getting errors stating that the FTP isn’t setup (I don’t think I saw that in older versions) I found the send by SFTP flag in config, so unchecked that. Only discovered that with it not checked the file doesn’t get put in x12_tracker. If the option is on then I have that race condition. I decided to put fake data in the x12 partners entry for ftp stuff. That kinda works but gives errors in php logs and I think will be the same race condition.
Looks like REST API is becoming the future where many are abandoning FTP.
We probably need to have a set up in partners. I don’t remember how I used for my eligibility stuff.
Still it seems important enough that if you show exactly what is needed, I’ll make the modification or you can put up a PR and I’ll help get in.
If we make it generic enough it can be easily adapted for any parameters. I’m not sure what I require will be what someone else does. Seems like the way to authenticate to a rest api is all over the place. Just a few examples… One place I connect to requires a key put in the header (seems out dated) another requires ssl cert and I do the client ID and Secret. So it’s everywhere just for authentication.
So, I think maybe just an additional flag in the x12_partners screen that says “add to remote tracker”. The SFTP service then could remain off and my module or any other could take it from there.
I’m currently adjusting my module only to pull out of the x12 tracker table the records that are assigned to it.
If you want to talk it through in voice let me know I’ll be happy to find the best solution.