Re: App review: myCRMSIM — 26 days pending, requesting reviewer assignment

Questions
1

Hi Make QA team,

myCRMSIM (v1.0.0) was submitted on 22 April 2026 and has now been pending for 26 days. I addressed the only feedback received (the 22/04 “Changes required” form completion) the same day. Since then, every status update has been “Request received” with no reviewer assigned (Reviewer field still shows TBS).

This is blocking a live customer rollout on our end, so I’d appreciate clarity on next steps.

The app meets all published prerequisites — sanitization, error handling, universal module, correct labels/descriptions, formatted dates, pagination, and a working invalid-credentials error path. All three test scenarios (5397330, 5392872, 5509881) have just been re-run and have fresh logs ready for inspection. API documentation is linked in the review form.

Could you please:

  1. Assign a QA reviewer, or share an expected timeline
  2. Confirm whether anything is missing on my side

If there’s a faster channel than this thread (a developer support contact, partner manager, etc.), I’d be grateful for the pointer.

Thanks,
[Your name]
JAG Digital
developers@jagdigital.com.au

4

Hey there @Developers1 :waving_hand:

Thanks for reaching out to us!

I’ve raised this internally, and one of my colleagues has reached out to you with the next steps. Check your inbox, and you should see their reply!

Let me know if there’s anything else I can help with :folded_hands:

5

Hi Vendy,

Thank you for escalating this internally — much appreciated.

One issue on my end: I’ve checked thoroughly (inbox, spam, and other folders) and nothing has come through from your colleague yet. Could you confirm the email address they sent it to, and roughly when it went out? The address on file is developers@jagdigital.com.au.

Since this is currently blocking a live customer rollout, I want to make sure nothing slips through the cracks. If easier, I’m also happy to be looped in directly via reply here.

Thanks for your help

6

Screenshot 2026-05-21 095757
Screenshot 2026-05-21 0957571536×894 72.7 KB

I Have send This email also but still not showing any response.

7

Hey there @Developers1 :waving_hand:

Thanks for the update! Don’t worry, we didn’t forget about you :smile: .
Our developers have the approval of your app on their to-do lists, and they will get to it - there are just a lot of apps to approve.

Thank you for your patience!

8

Hi Vendy :waving_hand:,

Just a gentle follow-up — it’s been a couple of weeks since I submitted my updated app for re-review, and I wanted to check if there’s any progress or if anything is needed from my side.

For reference, the public API documentation is here:

Completely happy to keep waiting — just wanted to make sure my submission hasn’t slipped through. Thank you so much for the support! :folded_hands:

Kind regards,
Gary Capps

image
image1891×719 63.6 KB

9

Hey there,

Thanks for raising this with me again. I see that your app has been approved and is now live! Congratulations :smiley:.

I’ll go ahead and close this topic. If there’s anything else I can help with, let me know.

10

**Live app needs developer assigned for small post-approval patch — myCRMSIM
**
Hi @vendy :waving_hand:,

First, thank you again for your help during the review process — myCRMSIM was approved on 29 May and is now live in the Make app library. Really appreciate the team’s support :folded_hands:

I’m reaching out because after release I discovered an issue affecting public users, and I need a developer assigned so the patch can be reviewed and pushed live.

The issue (for public users):

When new public users try to create a myCRMSIM connection in any scenario, they receive this error from our backend:

client_id and redirect_uri are required

After investigation, I found that the Common Data values (clientId, clientSecret) we configured during the original review do not appear to be passed through to public users — they resolve to empty strings on the user side, so the OAuth authorize request fails at our backend before login.

For me (the app owner / dev workspace), the connection works fine because my dev environment has access to Common Data. So the issue is only visible to public users in the marketplace.

The fix (already applied in my dev workspace):

I moved the clientId and clientSecret directly into the Connection Communication code (in the authorize qs and the token/refresh Basic auth header), replacing the {{common.clientId}} and {{common.clientSecret}} references. No other behavior, scope, or endpoint changes — only credential resolution.

This is the only change in this update.

What I’ve done so far:

  • :white_check_mark: Updated the Connection Communication code in the Make platform
  • :white_check_mark: Make’s UI shows: “Changes are only effective in your account. To apply these changes globally, go to the Review tab and submit the app for review.”
  • :white_check_mark: Submitted the changes for review via the Review tab
  • :white_check_mark: Sent an email to Levs B explaining the patch
  • :hourglass_not_done: Reviewer field currently shows “TBS” (To Be Assigned)

My request:

Could a developer please be assigned to review this small patch? Public users are currently blocked from creating new connections, so a quick turnaround would be hugely appreciated.

I’m happy to:

  • Provide more technical details or screenshots
  • Make adjustments if there’s a preferred way to keep Common Data while still passing it to public users
  • Hop on a call if helpful

Reference details:

  • App: myCRMSIM [v1.0.0]
  • Case ID: 2099406:2082001
  • Original reviewer: Levs B
  • Approval date: 29 May 2026
  • Patch submission date: [TODAY’S DATE]
  • Public API docs: myCRMSIM API Documentation

Thanks so much for your help, Vendy! :folded_hands:

Kind regards,
Gary Capps