502 Bad Gateway while creating polling Trigger in webmethods.io

, ,
1

Hi,

I am trying to create a polling trigger to pull the updates from Salesforce using wm.io Trigger in my workflow. But while testing the trigger, I am getting “502 Bad Gateway” . Below is the error message for the same:-

image
image916×317 17 KB

Can you let me know, what needs to be done?

Thanks in advance!

2

Hello Atul,

Sounds like an issue to me, verified at my end received 502 bad gateway error.

Regards,
Bharath

3

Hi Bharath,

Any suggestions to resolve this?

4

Hello Atul,

Checking the same, will update you shortly.

Regards,
Bharath

5

Thanks. Just some more points to add while you are looking at it:-

  1. The polling trigger does not work consistently. Say, If the interval is 5 mins, it should poll every 5 mins automatically. But unfortunately, it is not happening. It works sometime when i execute manually. But not happening automatically.
  2. Whenever i try to test the polling trigger, it ONLY tests it with the sample data, not the Account data. By account data, I mean the Salesforce data.
  3. Establishing/testing fresh connection is taking a lot of time.

Hoping I didn’t write/ask too much. :slight_smile:

Thanks in advance!!

6

Hello Atul,

No you are asking too much :wink: Indeed it could be potential platform issue.
Raised internal defect to track the same and will keep you updated with the status here.

Thank you.

Regards,
Bharath

2 Likes
7

:see_no_evil:. Np. Just thought to be a bit descriptive about the issue since we are trying to implement it for one of our client.

Anyways, thanks for raising the internal defect. :+1:. Will wait for your further updates.

Thanks and regards,
Atul Kumar Jha

8

Hi @Bharath_Meka1 ,

Did we find any workaround or solution to this?

Thanks,
Atul Kumar Jha

9

Hello Atul,

Currently the feature is all implemented and the testing is under progress in the lower environment. So far the testing has indicated positive trends and we are making good progress.

We are expected to complete all the testing by End of this week or early next week.

Once the Testing is complete we will update the plans on how and when the official fix will deployed to the production.

Will keep you posted with the updates.

Regards,
Bharath

10

Hi @Bharath_Meka1 ,

Many thanks for the update! Looking forward to the official fix. :+1:

11

Any further update on this official fix release date team? :slight_smile:

TIA,
RMG

12

Hello @RMG @atjha ,

Issue is fixed now, and yet to be rolled out to all tenants.

I will update here once it is completed.

Regards,
Bharath

13

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.